Actually the data on raid0 is not my data but of my users and they knew
and accepted the risk for raid0. So in my case it should be ok - I don't
know the importance of the data files which are affected. I just wanted
to help finding a possible bug and experiment with a broken btrfs
filesystem
Alexander Fieroch posted on Mon, 26 Nov 2018 11:23:00 +0100 as excerpted:
> Am 26.11.18 um 09:13 schrieb Qu Wenruo:
>> The corruption itself looks like some disk error, not some btrfs error
>> like transid error.
>
> You're right! SMART has an increased value for one harddisk on
> reallocated
Am 26.11.18 um 09:13 schrieb Qu Wenruo:
The corruption itself looks like some disk error, not some btrfs error
like transid error.
You're right! SMART has an increased value for one harddisk on
reallocated sector count. Sorry, I missed to check this first...
I'll try to salvage my data...
/dev/sdd errs: wr 0, rd 0, flush 0,
> corrupt 4, gen 1
> BTRFS error (device sdc): scrub: tree block 858820505600 spanning
> stripes, ignored. logical=3D858820444160
> BTRFS error (device sdc): scrub: tree block 858820505600 spanning
> stripes, ignored. logical=3D858820509696
> BTR
. logical=3D858820509696
BTRFS error (device sdc): unable to fixup (regular) error at logical
858803961856 on dev /dev/sdd
BTRFS error (device sdc): scrub: tree block 858821292032 spanning
stripes, ignored. logical=3D858821230592
BTRFS error (device sdc): scrub: tree block 858821292032 spanning
stripes
El 2014-10-29 04:02, Duncan escribió:
Juan Orti posted on Tue, 28 Oct 2014 16:54:19 +0100 as excerpted:
[ 3713.086292] BTRFS: unable to fixup (regular) error at logical
483011874816 on dev /dev/sdb2
[ 3713.092577] BTRFS: checksum error at logical 483011948544 on dev
/dev/sdb2, sector 628793528
On Oct 29, 2014, at 2:08 AM, Juan Orti juan.o...@miceliux.com wrote:
El 2014-10-29 04:02, Duncan escribió:
Juan Orti posted on Tue, 28 Oct 2014 16:54:19 +0100 as excerpted:
[ 3713.086292] BTRFS: unable to fixup (regular) error at logical
483011874816 on dev /dev/sdb2
[ 3713.092577] BTRFS
I'm seeing these errors in a RAID1 fs:
[ 3565.073223] BTRFS: bdev /dev/sdb2 errs: wr 0, rd 0, flush 0, corrupt
30, gen 0
[ 3565.073472] BTRFS: unable to fixup (regular) error at logical
460632743936 on dev /dev/sdb2
[ 3566.605419] BTRFS: checksum error at logical 461883383808 on dev
/dev/sdb2
El mar, 28-10-2014 a las 16:54 +0100, Juan Orti escribió:
I'm seeing these errors in a RAID1 fs:
(...)
Why can't it fix the errors? a bad device? smartctl says the disk is ok.
I'm currently running a full scrub to see if it finds more errors. What
should I do?
Well, the scrub has
Juan Orti posted on Tue, 28 Oct 2014 16:54:19 +0100 as excerpted:
[ 3713.086292] BTRFS: unable to fixup (regular) error at logical
483011874816 on dev /dev/sdb2
[ 3713.092577] BTRFS: checksum error at logical 483011948544 on dev
/dev/sdb2, sector 628793528, root 2500, inode 1436631, offset
, inode 1668516, offset 3473408,
length 4096, links 1 (path: path/to/some/file)
[101511.288676] btrfs: bdev /dev/sda3 errs: wr 0, rd 0, flush 0, corrupt
1, gen 0
[101511.291611] btrfs: unable to fixup (regular) error at logical
1590664605696 on dev /dev/sda3
[101511.390081] btrfs: checksum error
11 matches
Mail list logo
