View Incident:
http://co-op.engr.sgi.com/BugWorks/code/bwxquery.cgi?search=Search&wlong=1&view_type=Bug&wi=801063
Submitter : lord Submitter Domain : sgi.com
Assigned Engineer : nb Assigned Domain : sgi.com
Assigned Group : xfs-linux Category : software
Customer Reported : F Priority : 3
Project : xfs-linux Status : open
Description :
Running mkfs to build an xfs filesystem after a partition has
been mounted as ext2 has periodically failed for me. The failure
is usually this:
[root@lord /]# mkfs -t xfs -f -l size=16000b /dev/sda4
meta-data=/dev/sda4 isize=256 agcount=8, agsize=149104 blks
data = bsize=4096 blocks=1192826, imaxpct=25
= sunit=0 swidth=0 blks, unwritten=0
naming =version 2 bsize=4096
log =internal log bsize=4096 blocks=16000
realtime =none extsz=65536 blocks=0, rtextents=0
mkfs.xfs: write failed: No space left on device
The sequence of events was as follows:
1. mounted partition as xfs, ran some tests, unmounted
2. mkfs as ext2 using e2fsprogs-1.18-5 based commands
3. mount as ext2 and run some tests, unmount
4. do mkfs as xfs and fail.
This happens with top of trunk code and it is the write into the
last block of the device which fails.
fdisk says this about the device partition table:
Device Boot Start End Blocks Id System
/dev/sda1 * 1 66 530113+ 83 Linux
/dev/sda2 67 83 136552+ 82 Linux swap
/dev/sda3 84 512 3445942+ 83 Linux
/dev/sda4 513 1106 4771305 83 Linux
sda4 is the target.
Here is the strace output from the failure:
_llseek(4, 4885815296, [4885815296], SEEK_SET) = 0
write(4, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 512) = -1
ENOSPC (No space left on device)
|