Re: fsck of large volume with small memory

On 25 Sep, sam wrote:
Don Lewis wrote:
On 24 Sep, sam wrote:


any solutions ?


The patch below should allow a manual fsck to run to completion. I'd
recommend running "fsck -N" and capturing its output. Then use the clri

# fsck -N
fsck: illegal option -- N
usage: fsck [-dfnpvy] [-B | -F] [-T fstype:fsoptions] [-t fstype]
[special | node] ...

Sorry, it should be "fsck -n".

_______________________________________________
freebsd-hackers@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@xxxxxxxxxxx"

Relevant Pages

  • Re: Urgent Help Filesystem corrupted (automatic fsck failed)
    ... checking root file system.... ... /contains a file system with errors check forced ... Then I get taken to the command line to do manual fsck. ...
    (Ubuntu)
  • fsck: cannot find inode X
    ... Tonight, a server crashed and, when it came up, required a manual fsck. ... Normally, this is not a big deal, especially on our customer web servers, ... and would find the inode on my own. ...
    (freebsd-questions)