Disclaimer One or more of the links above will take you outside the Hewlett-Packard website.
so i should use the list i got from badblocks with dd but with bs=1024? If you are unable to mount the filesystem, then use the xfs_repair … Hi list, I recently I had a failed disk in a raid6 setup, which resulted in an IO error, which in turn caused XFS to shut down with the messages below. Return address = 00000000537fefdc xxxxxx kernel: XFS (dm-15): Please unmount the filesystem and rectify the problem(s) end_request: I/O error, dev sde, sector 39444095352 The system can not retrieve data located on sde at LBA address 39444095352 . Hence the first thing we need to do is reliable detection of errors and corruption. end_request: I/O error, dev sde, sector 39444095352 The system can not retrieve data located on sde at LBA address 39444095352 . I've seen on this list that incorrect use of xfs_repair might damage the fs even more, so I would like to ask for some advice on the best way to proceed. From: Ric Moore
Disk failure, XFS shutting down, trying to recover as much as possible. If you want you can add the -n parameter when running xfs_repair which will carry out a dummy run that actually makes no change to the disk if you want to see if xfs_repair thinks anything would need fixing. FIX: Run xfs_repair: # xfs_repair Yesterday I found out that my extra disk shut … I think I got that right. It is possible that the xfs_repair step is not necessary if the issue has been completely fixed by the mount/umount sequence. My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts. i'm not sure what is my block size, but xfs_info says this: debian:/# xfs_info /dev/md0 meta-data=/dev/md0 isize=256 agcount=32, agsize=5723342 blks = sectsz=512 attr=0 data = bsize=4096 blocks=183146912, imaxpct=25 = sunit=2 swidth=6 blks, unwritten=1 naming =version 2 bsize=4096 log =internal … SMART Attributes Data Structure revision number: 10 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 101 097 006 Pre-fail Always - 52655725 3 Spin_Up_Time 0x0003 093 093 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 … Firstly, we cannot repair a corruption we have not detected. Hi all, I’ve been struggling the past few days with XFS metadata corruption errors and I’m not sure how to proceed in troubleshooting the issue to narrow it down, or if I should try switching to another file system like ext4/btrfs/zfs, or if I’ve just set some parameters incorrectly. It sounds like you want me to try to do this same thing but rather than using \\\\tower\\FTP you want me to use \\\\tower\\diskx\\FTP? XFS metadata corruption and invalid checksum on SAP Hana servers This document (7022921) is provided subject to the disclaimer at the end of this document. This can be broken down into specific phases. $ sudo xfs_check /dev/sdb6 ERROR: The filesystem has valuable metadata changes in a log which needs to be replayed. The filesystem (see comment 7) shows NO errors when opened on the aarch64 machine.It only shows gross corruption errors when opened on x86_64 or armv7hl. Hi, since I upgraded from Centos5 to 6.5 I am having no end of trouble with a large raid array (Raid416S, Acnc) which has a xfs file system. Linux OS - Version Oracle Linux 7.0 and later: Oracle Linux 7: XFS Filesystem got Corrupted With "xfs_do_force_shutdown" Error Environment Reliable Detection and Repair of Metadata Corruption . I can run additional testing for you, but Im not sure what it is youre asking from your last post. Mount the filesystem to replay the log, and unmount it before re-running xfs_check. Re: Disk failure, XFS shutting down, trying to recover as much as possible. are you sure?