Hello!
I am not subscribed to this list. I just experienced an xfs fs shutting
down while putting heavy read/write load on the disks and simultaneously
growing the fs via xfs_growfs and I wanted to give someone the
opportunity to look after this, just in case I've spot a yet unknown
behaviour. My Linux Kernel is 2.6.8-2-686-smp (Debian packaged
kernel). I give you here the last lines from kern.log. If you are
interested, I could provide all log lines of this observation (over 500k
uncompressed) and additional information.
BTW: I was compiling 16 ISOs (14 CDR, 2 DVD) of Debian Sarge via jigdo
from a local lan mirror in parallel. :-)
Greets,
Wollie
Jun 22 22:00:29 amaranta kernel: dm-0: rw=0, want=1030768558088,
limit=146800640
Jun 22 22:00:29 amaranta kernel: I/O error in filesystem ("dm-0")
meta-data dev dm-0 block 0xeffe980002 ("xfs_trans_read_buf") error
5 buf count 512
Jun 22 22:00:29 amaranta kernel: attempt to access beyond end of device
Jun 22 22:00:29 amaranta kernel: dm-0: rw=0, want=1030772490248,
limit=146800640
Jun 22 22:00:29 amaranta kernel: I/O error in filesystem ("dm-0")
meta-data dev dm-0 block 0xeffed40002 ("xfs_trans_read_buf") error
5 buf count 512
Jun 22 22:00:29 amaranta kernel: attempt to access beyond end of device
Jun 22 22:00:29 amaranta kernel: dm-0: rw=0, want=1030776422408,
limit=146800640
Jun 22 22:00:29 amaranta kernel: I/O error in filesystem ("dm-0")
meta-data dev dm-0 block 0xefff100002 ("xfs_trans_read_buf") error
5 buf count 512
Jun 22 22:00:29 amaranta kernel: attempt to access beyond end of device
Jun 22 22:00:29 amaranta kernel: dm-0: rw=0, want=1030780354568,
limit=146800640
Jun 22 22:00:29 amaranta kernel: I/O error in filesystem ("dm-0")
meta-data dev dm-0 block 0xefff4c0002 ("xfs_trans_read_buf") error
5 buf count 512
Jun 22 22:00:29 amaranta kernel: attempt to access beyond end of device
Jun 22 22:00:29 amaranta kernel: dm-0: rw=0, want=1030784286728,
limit=146800640
Jun 22 22:00:29 amaranta kernel: I/O error in filesystem ("dm-0")
meta-data dev dm-0 block 0xefff880002 ("xfs_trans_read_buf") error
5 buf count 512
Jun 22 22:00:29 amaranta kernel: attempt to access beyond end of device
Jun 22 22:00:29 amaranta kernel: dm-0: rw=0, want=1030788218888,
limit=146800640
Jun 22 22:00:29 amaranta kernel: I/O error in filesystem ("dm-0")
meta-data dev dm-0 block 0xefffc40002 ("xfs_trans_read_buf") error
5 buf count 512
Jun 22 22:00:29 amaranta kernel: xfs_force_shutdown(dm-0,0x8) called
from line 1088 of file fs/xfs/xfs_trans.c. Return address = 0xf89fd44b
Jun 22 22:00:29 amaranta kernel: [__crc_pm_idle+749942/5290900]
xfs_ialloc_read_agi+0xf5/0x14a [xfs]
Jun 22 22:00:29 amaranta kernel: [__crc_pm_idle+743746/5290900]
xfs_ialloc_ag_select+0x2b1/0x340 [xfs]
Jun 22 22:00:29 amaranta last message repeated 2 times
Jun 22 22:00:29 amaranta kernel: [__crc_pm_idle+746719/5290900]
xfs_dialloc+0xb0e/0xb50 [xfs]
Jun 22 22:00:29 amaranta kernel: [__crc_pm_idle+819002/5290900]
xlog_grant_log_space+0x189/0x4f0 [xfs]
Jun 22 22:00:29 amaranta kernel: [__crc_pm_idle+775613/5290900]
xfs_ialloc+0x5c/0x4a0 [xfs]
Jun 22 22:00:29 amaranta kernel: [__crc_pm_idle+928262/5290900]
kmem_zone_zalloc+0x35/0x60 [xfs]
Jun 22 22:00:29 amaranta kernel: [__crc_pm_idle+883954/5290900]
xfs_dir_ialloc+0x91/0x2e0 [xfs]
Jun 22 22:00:29 amaranta kernel: [__crc_pm_idle+870677/5290900]
xfs_trans_reserve+0x84/0x1f0 [xfs]
Jun 22 22:00:29 amaranta kernel: [__crc_pm_idle+911902/5290900]
xfs_mkdir+0x2ad/0x740 [xfs]
Jun 22 22:00:29 amaranta kernel: [__crc_pm_idle+506124/5290900]
xfs_acl_vhasacl_default+0x3b/0x50 [xfs]
Jun 22 22:00:29 amaranta kernel: [__crc_pm_idle+958474/5290900]
linvfs_mknod+0x389/0x420 [xfs]
Jun 22 22:00:29 amaranta kernel: [tcp_v4_do_rcv+298/304]
tcp_v4_do_rcv+0x12a/0x130
Jun 22 22:00:29 amaranta kernel: [tcp_v4_rcv+1828/2496]
tcp_v4_rcv+0x724/0x9c0
Jun 22 22:00:29 amaranta kernel: [path_release+21/80]
path_release+0x15/0x50
Jun 22 22:00:29 amaranta kernel: [__crc_pm_idle+960122/5290900]
linvfs_permission+0x29/0x30 [xfs]
Jun 22 22:00:29 amaranta kernel: [__crc_pm_idle+958683/5290900]
linvfs_mkdir+0x2a/0x30 [xfs]
Jun 22 22:00:29 amaranta kernel: [vfs_mkdir+176/320] vfs_mkdir+0xb0/0x140
Jun 22 22:00:29 amaranta kernel: [sys_mkdir+184/256] sys_mkdir+0xb8/0x100
Jun 22 22:00:29 amaranta kernel: [syscall_call+7/11] syscall_call+0x7/0xb
Jun 22 22:00:29 amaranta kernel: xfs_force_shutdown(dm-0,0x1) called
from line 353 of file fs/xfs/xfs_rw.c. Return address = 0xf89fd44b
Jun 22 22:00:29 amaranta kernel: Filesystem "dm-0": Corruption of
in-memory data detected. Shutting down filesystem: dm-0
Jun 22 22:00:29 amaranta kernel: Please umount the filesystem, and
rectify the problem(s)
Jun 22 22:03:41 amaranta kernel: xfs_force_shutdown(dm-0,0x1) called
from line 353 of file fs/xfs/xfs_rw.c. Return address = 0xf89fd44b
Jun 22 22:04:49 amaranta kernel: xfs_force_shutdown(dm-0,0x1) called
from line 353 of file fs/xfs/xfs_rw.c. Return address = 0xf89fd44b
Jun 22 22:05:05 amaranta kernel: XFS mounting filesystem dm-0
Jun 22 22:05:05 amaranta kernel: Starting XFS recovery on filesystem:
dm-0 (dev: dm-0)
Jun 22 22:05:06 amaranta kernel: Ending XFS recovery on filesystem: dm-0
(dev: dm-0)
Jun 22 22:05:24 amaranta kernel: XFS mounting filesystem dm-0
Jun 22 22:05:24 amaranta kernel: Ending clean XFS mount for filesystem: dm-0
[[HTML alternate version deleted]]
|