hi, this box has had far too many hard reboots, but can anyone shed some light on whether this's inconsistent? i boot into single user mode, run fsck and fix all the partitions. rerunning fsck shows no more problems. mounting the filesystems and running fsck shows no problems. but when i reboot into normal mode, and run fsck on these 2 particular partitions: (and rebooting into single user mode again doesn't help). # fsck /tmp ** /dev/ad0s1e (NO WRITE) ** Last Mounted on /tmp ** Phase 1 - Check Blocks and Sizes ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts UNREF FILE I=83 OWNER=mysql MODE=100600 SIZE=0 MTIME=May 12 16:37 2006 CLEAR? no UNREF FILE I=84 OWNER=mysql MODE=100600 SIZE=0 MTIME=May 12 16:37 2006 CLEAR? no UNREF FILE I=85 OWNER=mysql MODE=100600 SIZE=0 MTIME=May 12 16:37 2006 CLEAR? no ** Phase 5 - Check Cyl groups 82 files, 540 used, 126299 free (27 frags, 15784 blocks, 0.0% fragmentation) # fsck /var ** /dev/ad0s1d (NO WRITE) ** Last Mounted on /var ** Phase 1 - Check Blocks and Sizes ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts UNREF FILE I=8314 OWNER=root MODE=100644 SIZE=0 MTIME=May 12 16:37 2006 CLEAR? no UNREF FILE I=8376 OWNER=root MODE=140666 SIZE=0 MTIME=May 12 16:37 2006 CLEAR? no ** Phase 5 - Check Cyl groups 1637 files, 37723 used, 89116 free (1252 frags, 10983 blocks, 1.0% fragmentation)
On Monday 15 May 2006 15:00, gareth wrote:> hi, this box has had far too many hard reboots, but can anyone shed some > light on whether this's inconsistent? i boot into single user mode,everything is mounted read-only,> run fsck and fix all the partitions. rerunning fsck shows no more problems. > mounting the filesystems and running fsck shows no problems. but when > i reboot into normal mode,where everything is mounted read-write for normal use> and run fsck on these 2 particular partitions: > (and rebooting into single user mode again doesn't help). >You cannot fsck a read-write mounted filesystem. The kernel is using it and will be in a state where fsck will think it has errors. Umount the filesystem first, check it then. ?lternatively you can snapshot it, and fsck -n the_snapshot HTH, Nikos
Hi. On Mon, May 15, 2006 at 02:00:57PM +0200, gareth wrote:> hi, this box has had far too many hard reboots, but can anyone shed some > light on whether this's inconsistent? i boot into single user mode, > run fsck and fix all the partitions. rerunning fsck shows no more problems. > mounting the filesystems and running fsck shows no problems. but when > i reboot into normal mode, and run fsck on these 2 particular partitions: > (and rebooting into single user mode again doesn't help).> # fsck /tmp > ** /dev/ad0s1e (NO WRITE)[...]> # fsck /var > ** /dev/ad0s1d (NO WRITE)Errm, You run fsck onto a r/w mounted partition on multiuser mode? If this understanding of what your saying here is correct, then this is the problem: a r/w mounted fs is a) never "clean" (in terms of a fsck that takes some time to run) because it changes with every operation and b) should never be checked in that way (that's exactly what fsck means when telling you "NO WRITE"). If a second fsck on the unmounted partition in single user does not show any problems anymore you can consider the filesystem clean. UFS2 (FreeBSD 5 and it's successors) can be checked "online" by fsck background mode (-B switch of fsck), but you should not need it. - Oliver -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 187 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20060515/be4d6e56/attachment-0001.pgp
On Mon 2006-05-15 (14:54), Oliver Brandmueller wrote:> Errm, You run fsck onto a r/w mounted partition on multiuser mode? Ifyep> this understanding of what your saying here is correct, then this is the > problem: a r/w mounted fs is a) never "clean" (in terms of a fsck that > takes some time to run)these 2 particular cases take 1 or 2 seconds> because it changes with every operation and b) > should never be checked in that way (that's exactly what fsck means when > telling you "NO WRITE").ok. but it didn't used to do this, then it started showing up errors on /var, then /var and /tmp. meanwhile the 5 other partitions have never showed up errors. (/tmp & /var i spose happen to be small and volatile, but there is another small & volatile partition that doesn't show errors. also, the same behaviour shows when i (think) get rid've processes using /tmp)