From: "Austin S. Hemmelgarn" <ahferroin7@gmail.com>
To: Daniel Brady <drbrady@gmail.com>, Roman Mamedov <rm@romanrm.net>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Chunk root problem
Date: Mon, 10 Jul 2017 08:59:54 -0400 [thread overview]
Message-ID: <3f7bfe3e-899e-a03e-0c85-c9c19ab40921@gmail.com> (raw)
In-Reply-To: <00581e84-6c8f-be60-94f9-2e88ca25e3fe@gmail.com>
On 2017-07-10 00:21, Daniel Brady wrote:
> On 7/7/2017 1:06 AM, Daniel Brady wrote:
>> On 7/6/2017 11:48 PM, Roman Mamedov wrote:
>>> On Wed, 5 Jul 2017 22:10:35 -0600
>>> Daniel Brady <drbrady@gmail.com> wrote:
>>>
>>>> parent transid verify failed
>>>
>>> Typically in Btrfs terms this means "you're screwed", fsck will not fix it, and
>>> nobody will know how to fix or what is the cause either. Time to restore from
>>> backups! Or look into "btrfs restore" if you don't have any.
>>>
>>> In your case it's especially puzzling as the difference in transid numbers is
>>> really significant (about 100K), almost like the FS was operating for months
>>> without updating some parts of itself -- and no checksum errors either, so
>>> all looks correct, except that everything is horribly wrong.
>>>
>>> This kind of error seems to occur more often in RAID setups, either Btrfs
>>> native RAID, or with Btrfs on top of other RAID setups -- i.e. where it
>>> becomes a complex issue that all writes to multi devices DO complete IN order,
>>> in case of an unclean shutdown. (which is much simpler on a single device FS).
>>>
>>> Also one of your disks or cables is failing (was /dev/sde on that boot, but may
>>> get a different index next boot), check SMART data for it and replace.
>>>
>>>> [ 21.230919] BTRFS info (device sdf): bdev /dev/sde errs: wr 402545, rd
>>>> 234683174, flush 194501, corrupt 0, gen 0
>>>
>>
>> Well that's not good news. Unfortunately I made a fatal error in not
>> having a backup. Restore looks like I could recover a good chunk of it
>> from the dry runs, however it has a lot of trouble reading many files.
>> I'm sure that is related to the one disk (sde). Drives were setup as raid56.
>>
>> After updating the kernel as suggested in the email from Duncan it
>> reduced the "parent transid verify" errors down to just one and the errs
>> on sde still exist.
>>
>> [ 21.400190] BTRFS info (device sdb): use no compression
>> [ 21.400191] BTRFS info (device sdb): disk space caching is enabled
>> [ 21.400192] BTRFS info (device sdb): has skinny extents
>> [ 21.584923] BTRFS info (device sdb): bdev /dev/sde errs: wr 402545,
>> rd 234683174, flush 194501, corrupt 0, gen 0
>> [ 23.394788] BTRFS error (device sdb): parent transid verify failed on
>> 5257838690304 wanted 591492 found 489231
>> [ 23.416489] BTRFS error (device sdb): parent transid verify failed on
>> 5257838690304 wanted 591492 found 489231
>> [ 23.416524] BTRFS error (device sdb): failed to read block groups: -5
>> [ 23.448478] BTRFS error (device sdb): open_ctree failed
>>
>> I ran a SMART test as you suggested with a passing result. I also
>> swapped SATA cables & power with another drive and the error followed
>> the drive confirmed by the serial via SMART. It seems like it just can't
>> read from that one drive for whatever reason. I also tried disconnecting
>> the drive and trying to mount it degraded with no luck. Still had the
>> transid error just with null as the bdev.
>>
>> smartctl -a /dev/sde
>> smartctl 6.2 2013-07-26 r3841 [x86_64-linux-4.12.0-1.el7.elrepo.x86_64]
>> (local build)
>> Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org
>>
>> === START OF INFORMATION SECTION ===
>> Model Family: Western Digital Red (AF)
>> Device Model: WDC WD30EFRX-68EUZN0
>> Serial Number: WD-WCC4N0PEYTEV
>> LU WWN Device Id: 5 0014ee 2b7dbfe54
>> Firmware Version: 82.00A82
>> User Capacity: 3,000,592,982,016 bytes [3.00 TB]
>> Sector Sizes: 512 bytes logical, 4096 bytes physical
>> Rotation Rate: 5400 rpm
>> Device is: In smartctl database [for details use: -P show]
>> ATA Version is: ACS-2 (minor revision not indicated)
>> SATA Version is: SATA 3.0, 6.0 Gb/s (current: 3.0 Gb/s)
>> Local Time is: Fri Jul 7 00:30:10 2017 MDT
>> SMART support is: Available - device has SMART capability.
>> SMART support is: Enabled
>>
>> === START OF READ SMART DATA SECTION ===
>> SMART overall-health self-assessment test result: PASSED
>>
>> General SMART Values:
>> Offline data collection status: (0x00) Offline data collection activity
>> was never started.
>> Auto Offline Data Collection:
>> Disabled.
>> Self-test execution status: ( 0) The previous self-test routine
>> completed
>> without error or no self-test
>> has ever
>> been run.
>> Total time to complete Offline
>> data collection: (40500) seconds.
>> Offline data collection
>> capabilities: (0x7b) SMART execute Offline immediate.
>> Auto Offline data collection
>> on/off support.
>> Suspend Offline collection upon new
>> command.
>> Offline surface scan supported.
>> Self-test supported.
>> Conveyance Self-test supported.
>> Selective Self-test supported.
>> SMART capabilities: (0x0003) Saves SMART data before entering
>> power-saving mode.
>> Supports SMART auto save timer.
>> Error logging capability: (0x01) Error logging supported.
>> General Purpose Logging supported.
>> Short self-test routine
>> recommended polling time: ( 2) minutes.
>> Extended self-test routine
>> recommended polling time: ( 406) minutes.
>> Conveyance self-test routine
>> recommended polling time: ( 5) minutes.
>> SCT capabilities: (0x703d) SCT Status supported.
>> SCT Error Recovery Control
>> supported.
>> SCT Feature Control supported.
>> SCT Data Table supported.
>>
>> SMART Attributes Data Structure revision number: 16
>> Vendor Specific SMART Attributes with Thresholds:
>> ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE
>> UPDATED WHEN_FAILED RAW_VALUE
>> 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always
>> - 0
>> 3 Spin_Up_Time 0x0027 179 179 021 Pre-fail Always
>> - 6050
>> 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always
>> - 15
>> 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always
>> - 0
>> 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always
>> - 0
>> 9 Power_On_Hours 0x0032 092 091 000 Old_age Always
>> - 6337
>> 10 Spin_Retry_Count 0x0032 100 253 000 Old_age Always
>> - 0
>> 11 Calibration_Retry_Count 0x0032 100 253 000 Old_age Always
>> - 0
>> 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always
>> - 15
>> 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always
>> - 5
>> 193 Load_Cycle_Count 0x0032 197 197 000 Old_age Always
>> - 9084
>> 194 Temperature_Celsius 0x0022 122 114 000 Old_age Always
>> - 28
>> 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always
>> - 0
>> 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always
>> - 0
>> 198 Offline_Uncorrectable 0x0030 100 253 000 Old_age
>> Offline - 0
>> 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always
>> - 0
>> 200 Multi_Zone_Error_Rate 0x0008 100 253 000 Old_age
>> Offline - 0
>>
>> SMART Error Log Version: 1
>> No Errors Logged
>>
>> SMART Self-test log structure revision number 1
>> Num Test_Description Status Remaining
>> LifeTime(hours) LBA_of_first_error
>> # 1 Short offline Completed without error 00% 6337
>> -
>> # 2 Extended offline Aborted by host 90% 6337
>> -
>>
>> SMART Selective self-test log data structure revision number 1
>> SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
>> 1 0 0 Not_testing
>> 2 0 0 Not_testing
>> 3 0 0 Not_testing
>> 4 0 0 Not_testing
>> 5 0 0 Not_testing
>> Selective self-test flags (0x0):
>> After scanning selected spans, do NOT read-scan remainder of disk.
>> If Selective self-test is pending on power-up, resume after 0 minute delay.
>>
>> -Dan
>>
>
> Does anyone have any other guidance on what I can do to try and recover?
> I would like to try anything I can do before moving on. I did a btrfs
> restore and got what little I had left. btrfsck just gives me a "ERROR:
> failed to repair root items: Input/output error" and btrfs rescue
> zero-log does not seem to do anything.
Unfortunately, it sounds like the firmware or the controller on the disk
itself is bad. If the device is as young as the Power_On_Hours implies
(that lists less than a year of run-time), then it may still be under
warranty, and you might be able to get the manufacturer to fix the disk
for you, but other than that there's unfortunately not much you can do
if it is the firmware or controller.
Also, just as a side note, the reported flush errors for that device are
probably the reason that the transid verification is so far off.
next prev parent reply other threads:[~2017-07-10 13:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-06 4:10 Chunk root problem Daniel Brady
2017-07-06 9:26 ` Duncan
2017-07-07 5:48 ` Roman Mamedov
2017-07-07 7:06 ` Daniel Brady
2017-07-10 4:21 ` Daniel Brady
2017-07-10 12:59 ` Austin S. Hemmelgarn [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-07-07 6:08 Daniel Brady
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3f7bfe3e-899e-a03e-0c85-c9c19ab40921@gmail.com \
--to=ahferroin7@gmail.com \
--cc=drbrady@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=rm@romanrm.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.