http://bugzilla.kernel.org/show_bug.cgi?id=10421
Summary: Filesystem failing without any warning or etc
Product: File System
Version: 2.5
KernelVersion: 2.6.25-rc8-git1
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: high
Priority: P1
Component: XFS
AssignedTo: xfs-masters@xxxxxxxxxxx
ReportedBy: nuclearcat@xxxxxxxxxxxxxx
Latest working kernel version: 2.6.24.3
Earliest failing kernel version: 2.6.25-rc7-git3
Distribution: Custom
Hardware Environment: Sun Fire X4100
Software Environment: Customer distro with busybox tools, mount-2.12r
Problem Description:
Each night my proxy is crashing.
I notice that it's cannot open some cache directory. Before it was /cache4, but
after i remove it from configuration of squid and even unmounted it, /cache3
start to fail. All hardware is in good condition, and i have similar problem on
another proxy server, but it's more rare (not each night).
After analysing situation here is result:
ls /cache3 is empty, while it must be one directory, squid.
SUPERPROXY /cache3 # echo "xxx" >x
-ash: cannot create x: Input/output error
/dev/sde1 on /cache3 type xfs (rw,noatime,nodiratime,logbufs=8,noquota)
SUPERPROXY /cache3 # xfs_info /cache3
xfs_info: /cache3 is not a mounted XFS filesystem
SUPERPROXY /cache3 # cat /proc/mounts
rootfs / rootfs rw 0 0
proc /proc proc rw 0 0
sysfs /sys sysfs rw 0 0
none /dev/pts devpts rw,mode=600 0 0
none /proc/bus/usb usbfs rw 0 0
/dev/mapper/root /mnt/flash ext3 rw,noatime,errors=continue,data=ordered 0 0
/dev/sdc2 /cache1 xfs rw,noatime,nodiratime,logbufs=8,noquota 0 0
/dev/sdd1 /cache2 xfs rw,noatime,nodiratime,logbufs=8,noquota 0 0
/dev/sde1 /cache3 xfs rw,noatime,nodiratime,logbufs=8,noquota 0 0
SUPERPROXY ~ # umount /cache3
on dmesg appeared:
[261943.707659] xfs_force_shutdown(sde1,0x1) called from line 420 of file
fs/xfs/xfs_rw.c. Return address = 0xf8b79dd2
SUPERPROXY ~ # xfs_repair /dev/sde1
Phase 1 - find and verify superblock...
Phase 2 - using internal log
- zero log...
- scan filesystem freespace and inode maps...
- found root inode chunk
Phase 3 - for each AG...
- scan and clear agi unlinked lists...
- process known inodes and perform inode discovery...
- agno = 0
- agno = 1
- agno = 2
- agno = 3
- agno = 4
- agno = 5
- agno = 6
- agno = 7
- agno = 8
- agno = 9
- agno = 10
- agno = 11
- agno = 12
- agno = 13
- agno = 14
- agno = 15
- process newly discovered inodes...
Phase 4 - check for duplicate blocks...
- setting up duplicate extent list...
- check for inodes claiming duplicate blocks...
- agno = 0
- agno = 1
- agno = 2
- agno = 3
- agno = 4
- agno = 5
- agno = 6
- agno = 7
- agno = 8
- agno = 9
- agno = 10
- agno = 11
- agno = 12
- agno = 13
- agno = 14
- agno = 15
Phase 5 - rebuild AG headers and trees...
- reset superblock...
Phase 6 - check inode connectivity...
- resetting contents of realtime bitmap and summary inodes
- traversing filesystem ...
- traversal finished ...
- moving disconnected inodes to lost+found ...
disconnected inode 471077370, moving to lost+found
Phase 7 - verify and correct link counts...
done
SUPERPROXY /cache3/lost+found # ls -la
drwxr-xr-x 2 root root 38 Apr 3 08:49 .
drwxr-xr-x 4 squid root 35 Apr 6 2007 ..
-rw-r----- 1 squid squid 0 Apr 1 00:38 336079762
-rw-r----- 1 squid squid 0 Mar 19 07:11 471077370
Steps to reproduce: Difficult, i didn't found any reason why it is crashing.
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
|