Re: fsck of large volume with small memory

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] ...

/Vladimir Ermakov

_______________________________________________
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: Undeletable files on ext2
    ... > And if I try to delete the file with the root account, ... "Clri is obsoleted for normal file system repair work by fsck." ... to clri and immediately reboot single user, ... run your normal fsck which will report ...
    (comp.os.linux.misc)
  • Re: Remove a file by inode number?
    ... >> apart from my boot drive... ... > Read the clri man page and use fsck instead. ... The problem was fsck couldn't fix the error so I needed another ... Prev by Date: ...
    (uk.comp.sys.mac)
  • forcefsck on booting stage
    ... How to make 'fsck -f' on booting stage of remote system? ... /Vladimir Ermakov ...
    (freebsd-hackers)