On Sun, Jul 07, 2002 at 09:41:14PM -0700, Peter Wemm wrote: > It seems to be aborting the 'process all file systems' loop when it modifies > a file system. eg:
<...> > [[[ Uhh, what? What about the rest of the file systems? ]]] I saw this once yesterday night, (after getting an "automagic reboot" while running Mozilla... is this a new kind of anti-porn device?:-P) and was puzzzled seeing that as well. But interestingly, after this I just persisted and issued "fsck -y" again and this time it ran as it should. While we are here: while "fsck -y" returns the fragmentation etc values correctly, "fsck -p" always says: "0.0 % fragmentation" for all my filesystems. Like this: /dev/ad1s1a: FILESYSTEM CLEAN; SKIPPING CHECKS /dev/ad1s1a: clean, 1016302 free (14 frags, 0 blocks, 0.0% fragmentation) Anyone else seen this? -- Regards: Szilveszter ADAM Szombathely Hungary To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
