Inconsistency in root partition size

[jaymax]

Mel Flynn-2 wrote:
> 
> On Sunday 06 September 2009 04:34:20 jaymax wrote:
>> I apparently have open file handles in my / partitions.
>> It was partitioned at 512 Mb size, used about 150Mb
>> df shows
>> Filesystem     Size    Used   Avail Capacity  Mounted on
>> /dev/ad0s1a    496M    492M    -36M   108%    /
> 
>> adjkerntz   147   root    0u    VBAD                              
>> (revoked) adjkerntz   147   root    1u    VBAD                             
> 
> 
>> Can't really identify lines I can say does not belong so I don't have any
>> rational basis to kill any process. All seems legit!
>>
>> Rebooting does not correct the descrepancy
> 
> For one, you could've used fstat -f / to reduce the noise. Secondly, since 

You were correct fstat -f / showed no open files handles



rebooting does not help, open files are not the cause. Rather the VBAD up 
> there. Do an fsck -y. Chances are your file system got filled, a hardware 
> write error occurred and the kernel could therefore not return the space
> to 
> the disk.
> If you still have logs, I would grep for WRITE_DMA in 
> 

ran fsck on / mounted partition, is that reasonable or possible, since it is
/ or do I have to use a livefs disk like Fixit or Frenzy for this

# fsck -vy -B /dev/ad0s1a
start / wait fsck_ufs -y -F /dev/ad0s1a
start / wait fsck_ufs -y -B /dev/ad0s1a

/: write failed, filesystem is full
CANNOT CREATE SNAPSHOT //.snap/fsck_snapshot: No space left on device
** /dev/ad0s1a (NO WRITE)
** Last Mounted on /
** Root file system
** Phase 1 - Check Blocks and Sizes
** Phase 2 - Check Pathnames
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
UNREF FILE  I=3417  OWNER=root MODE=100400
SIZE=0 MTIME=Sep  6 02:41 2009 
RECONNECT? no

CLEAR? no

UNREF FILE I=3495  OWNER=root MODE=140666
SIZE=0 MTIME=Sep  5 01:17 2009 
CLEAR? no

UNREF FILE  I=3524  OWNER=root MODE=100644
SIZE=154 MTIME=Sep  5 01:23 2009 
RECONNECT? no

CLEAR? no

** Phase 5 - Check Cyl groups
FREE BLK COUNT(S) WRONG IN SUPERBLK
SALVAGE? no

16849 files, 251849 used, 1966 free (1966 frags, 0 blocks, 0.8%
fragmentation)
-----
# grep -in WRITE_DMA /var/log/messages
Yielded nothing either

Rebooted - came back up with the same condition.

On rebooting, doesn't the system run fsck -y before mounting the disks

Still stuck, at least we have eliminated the "open file handler" belief

Thanks

-- 
View this message in context: http://www.nabble.com/Inconsistency-in-root-partition-size-tp25314145p25316313.html
Sent from the freebsd-questions mailing list archive at Nabble.com.