On Sun, 12 Sep 2010 16:16:53 -0500 (CDT)
Robert Bonomi wrote:
> There are exactly _four_ possible causes of file-system
> inconsistencies. 1) You can have an unexpected loss of power, where
> the CPU stops working before it as time to write the above-mentioned
> 'memory-resident' data to disk. T
> From owner-freebsd-questi...@freebsd.org Fri Sep 10 17:51:18 2010
> From: cronfy
> Date: Sat, 11 Sep 2010 02:27:46 +0400
> To: freebsd-questions
> Subject: fsck reports errors on clean filesystem (mounted rw)
>
> Hello.
>
> I ran fsck on my filesystems while system
On Sep 10, 2010, at 3:27 PM, cronfy wrote:
> 1. Can I be sure my filesystem is consistent?
Reasonably.
> 2. If fsck reports nonexistent errors (and probably will try to fix
> them if asked), isn't it even danger to run fsck on running system?
Running fsck in foreground mode on a mounted filesyst
Hello.
I ran fsck on my filesystems while system was running (partitons were
mounted rw with moderate FS usage). fsck reported there were errors
(INCORRECT BLOCK COUNT and others). I decided to reboot to single mode
and check all filesystems. But in single mode fsck did not find any
errors.
1. C
