Filesystem Sdb Xfs_log_force Error 5 Returned
Contents |
after IO error on raid device From: Roel van Meer
Kernel Filesystem Xfs_log_force Error 5 Returned
writes: Currently I have unmounted the filesystem, replaced the failed xfs error 5 disk and rebuilt the raid array. I am upgrading xfstools to their latest version (the xfs_log_force: error 5 returned redhat current version is 2.9.8). Any hints on how to continue would be highly appreciated. Trying to answer my own question. I _think_ this is the way
Ubuntu Xfs_log_force Error 5 Returned
to go: 1) Mount and unmount the fs, in order to replay the log. 2) Run xfs_repair -n 3) Run xfs_repair If someone could confirm (or reject) that, that would be great. (By the way, is it necessary to run xfs_repair with -n first? If not, are there advantages that would justify
Xfs_log_force Error 5 Returned Suse
the extra time it takes?) Thanks again, roel Jun 21 23:23:59 backup2 kernel: arcmsr6: abort device command of scsi id = 0 lun = 0 Jun 21 23:24:10 backup2 kernel: arcmsr6: ccb ='0xffff8800cb88ad40'????????????????????????????? isr got aborted command Jun 21 23:24:10 backup2 kernel: arcmsr6: isr get an illegal ccb command???????????????????????????????? done acb = '0xffff880231c90408'ccb = '0xffff8800cb88ad40' ccbacb = '0xffff880231c90408' startdone = 0x0 ccboutstandingcount = 1 Jun 21 23:24:10 backup2 kernel: sd 6:0:0:0: [sdb] Unhandled error code Jun 21 23:24:10 backup2 kernel: sd 6:0:0:0: [sdb] Result: hostbyte=DID_ABORT driverbyte=DRIVER_OK Jun 21 23:24:10 backup2 kernel: end_request: I/O error, dev sdb, sector 12887056410 Jun 21 23:24:10 backup2 kernel: I/O error in filesystem ("sdb1") meta-data dev sdb1 block 0x30020dff8?????? ("xfs_trans_read_buf") error 5 buf count 4096 Jun 21 23:24:10 backup2 kernel: xfs_force_shutdown(sdb1,0x1) called from line 414 of file fs/xfs/xfs_trans_buf.c.? Return address = 0xffffffffa0168eaf Jun 21 23:24:10 backup2 kernel: xfs_force_shutdown(sdb1,0x2) called from line 811 of file fs/xfs/xfs_log.c.? Return address = 0xffff
errors xfs: internal error xfs_want_corrupted_goto (XFS_WANT_CORRUPTED_GOTO) General support questions including new installations
Corruption Of In-memory Data Detected. Shutting Down Filesystem
Post Reply Print view Search Advanced search 11 posts 1 2 xfs_log_force error -5 returned Next adolphson Posts: 5 Joined: 2010/07/04 10:53:17 [SOLVED] XFS internal errors (XFS_WANT_CORRUPTED_GOTO) Quote Postby adolphson » 2010/07/04 12:24:58 Hi,We http://oss.sgi.com/archives/xfs/2010-06/msg00273.html have been able to repeatably produce xfs internal errors (XFS_WANT_CORRUPTED_GOTO) on one of our fileservers. We are attempting to locally copy a 248Gig file off a usb drive formated as NTFS to the xfs drive. The copy http://www.centos.org/forums/viewtopic.php?t=15898 gets about 96% of the way through and we get the following messages:Code: Select allJun 28 22:14:46 terrorserver kernel: XFS internal error XFS_WANT_CORRUPTED_GOTO at line 2092 of file fs/xfs/xfs_bmap_btree.c. Caller 0xffffffff8837446f
Jun 28 22:14:46 terrorserver kernel:
Jun 28 22:14:46 terrorserver kernel: Call Trace:
Jun 28 22:14:46 terrorserver kernel: [
Jun 28 22:14:46 terrorserver kernel: [
Jun 28 22:14:46 terrorserver kernel: [
Jun 28 22:14:46 terrorserver kernel: [
Jun 28 22:14:46 terrorserver kernel: [
Jun 28 22:14:46 terrorserver kernel: [
Jun 28 22:14:46 terrorserver kernel: [
Jun 28 22:14:46 terrorserver kernel: [
Jun 28 22:14:46 terrorserver kernel: [
Jun 28 22:14:4
Password Login: [x] Format For Printing -XML -Clone This Bug -Last Comment First Last Prev Next This bug is not in https://bugzilla.redhat.com/show_bug.cgi?id=820702 your last search results. Bug820702 - An xfs filesystem on a USB drive is not accessible after a machine suspend [NEEDINFO] Summary: An xfs filesystem on a USB drive is not accessible after a machine suspend Status: CLOSED INSUFFICIENT_DATA Aliases: None Product: Fedora Classification: Fedora Component: kernel (Show other bugs) Sub Component: --- Version: 19 Hardware: Unspecified Unspecified Priority unspecified Severity unspecified TargetMilestone: --- TargetRelease: error 5 --- Assigned To: Kernel Maintainer List QA Contact: Fedora Extras Quality Assurance Docs Contact: URL: Whiteboard: Keywords: Depends On: Blocks: Show dependency tree /graph Reported: 2012-05-10 13:53 EDT by Emmanuel Pacaud Modified: 2014-06-23 10:41 EDT (History) CC List: 7 users (show) esandeen gansalmon itamar jonathan kernel-maint madhu.chinakonda mchehab See Also: Fixed In Version: Doc Type: Bug Fix Doc Text: Story Points: --- Clone Of: error 5 returned Environment: Last Closed: 2014-06-23 10:41:24 EDT Type: Bug Regression: --- Mount Type: --- Documentation: --- CRM: Verified Versions: Category: --- oVirt Team: --- RHEL 7.3 requirements from Atomic Host: Cloudforms Team: --- Flags: jforbes: needinfo? Attachments (Terms of Use) /var/log/messages (23.61 KB, application/zip) 2012-05-10 14:08 EDT, Emmanuel Pacaud no flags Details Add an attachment (proposed patch, testcase, etc.) Groups: None (edit) Description Emmanuel Pacaud 2012-05-10 13:53:24 EDT After a machine suspend, my USB hdd, formated using the xfs format, is not accessible from nautilus. Here is what nautilus says: "Could not display "/run/media/manu/Rackham". Error: Error when getting information for file '/run/media/manu/Rackham': Input/output error Please select another viewer and try again." Here is what is in /var/log/messages: May 10 17:03:29 hobbes NetworkManager[626]: