Re: file system trouble
The /home filesystem was full (121G partition on a 3ware escalade raid) So i deleted 7G, but df did not show any difference. The fs is mounted w/ soft-updates. I issued a sync command, but still no change. The files were no longer shown in ls, but space was not freed. So i decided to reboot, to make sure that the deleted files are not still opened by some process. The shutdown went normal, but at the end it said: sysncing disks.. 3321 3321 3321 3316 . giving up on 1 buffers. When rebooting, all fs were unclean and i had to wait the usual 20 minutes for fsck to complete. I've seen the same 'df' situation when softupdates are enabled, but I've never tried to resolve the problem with a reboot. I just ignore the 'df' output, and proceed normally. After some time passes, 'df' returns to reporting the expected values. I've always thought this was normal with softupdates. However, I've not had your problem with the fsck, but then again... I've not rebooted soon after deleting 7GB of data from a file system. What are you running? 4.6.2, 4.7, -current? --daxbert To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: file system trouble
Daxbert wrote: The /home filesystem was full (121G partition on a 3ware escalade raid) So i deleted 7G, but df did not show any difference. The fs is mounted w/ soft-updates. I issued a sync command, but still no change. The files were no longer shown in ls, but space was not freed. So i decided to reboot, to make sure that the deleted files are not still opened by some process. The shutdown went normal, but at the end it said: sysncing disks.. 3321 3321 3321 3316 . giving up on 1 buffers. When rebooting, all fs were unclean and i had to wait the usual 20 minutes for fsck to complete. I've seen the same 'df' situation when softupdates are enabled, but I've never tried to resolve the problem with a reboot. I just ignore the 'df' output, and proceed normally. After some time passes, 'df' returns to reporting the expected values. I've always thought this was normal with softupdates. However, I've not had your problem with the fsck, but then again... I've not rebooted soon after deleting 7GB of data from a file system. What are you running? 4.6.2, 4.7, -current? I use 4.6.2-RELEASE (wrote it in my first post :-) The problem was not only the 'df' output, but that i actually i could not create any files! (disk full) My main question is: Why did the sysnc on shutdown not succeed, leaving all my fs dirty? Heinrich To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: file system trouble
Heinrich Rebehn wrote: [ ... ] The /home filesystem was full (121G partition on a 3ware escalade raid) So i deleted 7G, but df did not show any difference. The fs is mounted w/ soft-updates. I issued a sync command, but still no change. The files were no longer shown in ls, but space was not freed. Was some process holding those files open? The space doesn't get freed until that process terminates. So i decided to reboot, to make sure that the deleted files are not still opened by some process. The shutdown went normal, but at the end it said: syncing disks.. 3321 3321 3321 3316 . I dont't know the exact numbers anymore, but it printed some 40x80 lines of 4 digit numbers, the last line was all 1s and then said: When you rebooted, your system had ~3300 buffers of data that had not yet been written to disk. It was able to write almost all of them out to disk, but it failed with one: giving up on 1 buffers. When rebooting, all fs were unclean and i had to wait the usual 20 minutes for fsck to complete. Yes. FreeBSD probably should have marked the other filesystems (except for the one with the open buffer) as clean. But fsck'ing after a moderately serious problem-- even if you may not have really needed to-- is a fail-safe approach. -Chuck To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
