Hi Otto, fsck -p is not possible to do in multi-user because of
# fsck -p /extra NO WRITE ACCESS /dev/rwd0m: UNEXPECTED INCONSISTENCY; RUN fsck_ffs MANUALLY. I haven't checked but it probably wants to do it single user when all fs are unmounted. And it would work when fs are unclean shutdown. I applied art@ diff and the exact same partition (which I newfs'd with the original defaults -b 16K -f 2K), went through fsck within 1 minute (I copied original /sbin/fsck_ffs to /sbin/ofsck_ffs). I have enabled bigmem, and his diff is absolutely needed for fast fsck. Thank you Arthur and the team for a very fast turnaround! Thank you for reducing the pain. I will schedule a fsck every month or so, knowing it won't screw up anything and be done really quick. So with the information presented in this thread, fsck shouldn't be a problem for anybody anymore. That is, increasing data block size (say for Postgres or for Virtual images or family videos) and checking only used inodes. Thanks, amit > Please tell us more why -p does not work. What happens if you try it. > Be more exact in your description. > > So why is you system extra slow? Maybe it has too little memory and > starts swapping. Some details might come in handy.
