Starting with 2.6.4-xfs (CVS) I have "Log reservation ran out" error.
This is a 150GB NFS exported software raid 5 device with version 2 logs.
XFS mounting filesystem md0
Ending clean XFS mount for filesystem: md0
Filesystem "md0": xfs_log_write: reservation ran out. Need to up reservation
xfs_force_shutdown(md0,0x8) called from line 1693 of file
fs/xfs/xfs_log.c. Return address = 0xc01efe4a
Filesystem "md0": Corruption of in-memory data detected. Shutting down
filesystem: md0
Please umount the filesystem, and rectify the problem(s)
xfs_force_shutdown(md0,0x2) called from line 1291 of file
fs/xfs/xfs_log.c. Return address = 0xc01efe4a
The filesystem reports no problems in xfs_repair after mounting and
unmounting the filesystem.
lsautom:~# xfs_info /raid/
meta-data=/raid isize=256 agcount=37, agsize=1048568 blks
= sectsz=512
data = bsize=4096 blocks=38399936, imaxpct=25
= sunit=1 swidth=3 blks, unwritten=0
naming =version 2 bsize=4096
log =internal bsize=4096 blocks=32768, version=2
= sectsz=512 sunit=8 blks
realtime =none extsz=65536 blocks=0, rtextents=0
Apart from the swidth parameter being incorrect I don't see much wrong with it.
IO on the drive is very light and seems to be triggered by the nightly
backups. The volume in question is not backed up which makes it even
weirder. It just passes by the mountpoint.
I have added the debugging flags for a stack trace and I will try to make
it fall over.
Cheers
--
Seth
I don't make sense, I don't pretend to either. Questions?
|