Project

General

Profile

Actions
Copy link

Bug #1311

closed

XFS error on bilbo2

Added by Alexander Werner almost 9 years ago. Updated almost 9 years ago.

Status:
Closed
Priority:
Immediate
Assignee:
-
Category:
-
Target version:
-
Start date:
Due date:
% Done:

0%

Tags:
URL:

Description

From syslog:

Jun 11 12:03:00 bilbo2 kernel: [3631536.361584] XFS (dm-5): Corruption detected. Unmount and run xfs_repair
Jun 11 12:03:00 bilbo2 kernel: [3631536.361627] XFS (dm-5): xfs_iunlink_remove: xfs_itobp() returned error 117.
Jun 11 12:03:00 bilbo2 kernel: [3631536.361630] XFS (dm-5): xfs_inactive: xfs_ifree returned error 117
Jun 11 12:03:00 bilbo2 kernel: [3631536.361634] XFS (dm-5): xfs_do_force_shutdown(0x1) called from line 745 of file /build/buildd/linux-3.2.0/fs/xfs/xfs_vnodeops.c.  Return address = 0xffffffffa017e71f
Jun 11 12:03:00 bilbo2 kernel: [3631536.375037] XFS (dm-5): I/O Error Detected. Shutting down filesystem
Jun 11 12:03:00 bilbo2 kernel: [3631536.375076] XFS (dm-5): Please umount the filesystem and rectify the problem(s)

After reboot, metadata log was replayed and filesystem has recovered.
It is necessary to investigate source of the issue.

Actions
Copy link
 #1

Updated by Alexander Werner almost 9 years ago

  • Status changed from New to Closed

Okay, its a corrupted unlinked inode list. Bug is specific to ubuntu precise and amazon AWS kernels in version 3.2, unkown what triggered it, probably won't be fixed ever. Does not occur in newer kernel versions. A reboot fixes the FS automatically.

Actions
Copy link

Also available in: Atom PDF