Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-14871

Better error message for FileAllocator failure

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Minor - P4
    • Resolution: Gone away
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Diagnostics, Storage
    • Labels:

      Description

      In database_holder.cpp we have the following code:

              if (txn->lockState()->isWriteLocked() && FileAllocator::get()->hasFailed()) {
                  uassert(17507, "Can't take a write lock while out of disk space", false);
              }
      

      If FileAllocator may fail for other reasons (e.g.: the dbpath is on a network drive and there was a network problem) then this message is misleading.

      Something like "Can't take a write lock: FileAllocator failed" would be a better message; if we could provide more info about the failure somehow, that would be even better.

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                6 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: