All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Petrini <john.d.petrini@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: Filesystem Went Read Only During Raid-10 to Raid-6 Data Conversion
Date: Tue, 14 Jul 2020 12:13:56 -0400	[thread overview]
Message-ID: <CADvYWxeiNynEWUYwfQxP7fQTK4k2Q+eDZsA8j7rLcaTSeND9fg@mail.gmail.com> (raw)

Hello All,

My filesystem went read only while converting data from raid-10 to
raid-6. I attempted a scrub but it immediately aborted. Can anyone
provide some guidance on possibly recovering?

Thank you!

##System Details##
Ubuntu 18.04

# This shows some read errors but they are not new. I had a SATA cable
come loose on a drive some months back that caused these. They haven't
increased since I reseated the cable
sudo btrfs device stats /mnt/storage-array/ | grep sde
[/dev/sde].write_io_errs    0
[/dev/sde].read_io_errs     237
[/dev/sde].flush_io_errs    0
[/dev/sde].corruption_errs  0
[/dev/sde].generation_errs  0


btrfs fi df /mnt/storage-array/
Data, RAID10: total=32.68TiB, used=32.64TiB
Data, RAID6: total=1.04TiB, used=1.04TiB
System, RAID10: total=96.00MiB, used=3.06MiB
Metadata, RAID10: total=40.84GiB, used=39.94GiB
GlobalReserve, single: total=512.00MiB, used=512.00MiB

uname -r
5.3.0-40-generic

##dmesg##
[3813499.479570] BTRFS info (device sdd): no csum found for inode
44197278 start 401276928
[3813499.480211] BTRFS warning (device sdd): csum failed root 5 ino
44197278 off 401276928 csum 0x0573112f expected csum 0x00000000 mirror
2
[3813506.750924] BTRFS error (device sdd): parent transid verify
failed on 98952926429184 wanted 6618521 found 6618515
[3813506.751395] BTRFS error (device sdd): parent transid verify
failed on 98952926429184 wanted 6618521 found 6618515
[3813506.751783] BTRFS info (device sdd): no csum found for inode
44197278 start 152698880
[3813506.773031] BTRFS warning (device sdd): csum failed root 5 ino
44197278 off 152698880 csum 0x9b7d599f expected csum 0x00000000 mirror
1
[3813506.773070] BTRFS error (device sdd): parent transid verify
failed on 98952926429184 wanted 6618521 found 6618515
[3813506.773596] BTRFS error (device sdd): parent transid verify
failed on 98952926429184 wanted 6618521 found 6618515
[3813506.774073] BTRFS info (device sdd): no csum found for inode
44197278 start 152698880
[3813506.813401] BTRFS warning (device sdd): csum failed root 5 ino
44197278 off 152698880 csum 0x9b7d599f expected csum 0x00000000 mirror
2
[3813506.813431] BTRFS error (device sdd): parent transid verify
failed on 98952926429184 wanted 6618521 found 6618515
[3813506.813439] BTRFS error (device sdd): parent transid verify
failed on 98952926429184 wanted 6618521 found 6618515
[3813506.813444] BTRFS info (device sdd): no csum found for inode
44197278 start 152698880
[3813506.813612] BTRFS warning (device sdd): csum failed root 5 ino
44197278 off 152698880 csum 0x9b7d599f expected csum 0x00000000 mirror
3
[3813506.813624] BTRFS error (device sdd): parent transid verify
failed on 98952926429184 wanted 6618521 found 6618515
[3813506.813628] BTRFS error (device sdd): parent transid verify
failed on 98952926429184 wanted 6618521 found 6618515
[3813506.813632] BTRFS info (device sdd): no csum found for inode
44197278 start 152698880
[3813506.816222] BTRFS warning (device sdd): csum failed root 5 ino
44197278 off 152698880 csum 0x9b7d599f expected csum 0x00000000 mirror
4
[3813510.542147] BTRFS error (device sdd): parent transid verify
failed on 104091430649856 wanted 6618521 found 6618516
[3813510.542731] BTRFS error (device sdd): parent transid verify
failed on 104091430649856 wanted 6618521 found 6618516
[3813510.543216] BTRFS info (device sdd): no csum found for inode
44197278 start 288227328
[3813510.558299] BTRFS warning (device sdd): csum failed root 5 ino
44197278 off 288227328 csum 0xa0775535 expected csum 0x00000000 mirror
1
[3813510.558341] BTRFS info (device sdd): no csum found for inode
44197278 start 288227328
[3813510.574681] BTRFS warning (device sdd): csum failed root 5 ino
44197278 off 288227328 csum 0xa0775535 expected csum 0x00000000 mirror
2
[3813510.574714] BTRFS info (device sdd): no csum found for inode
44197278 start 288227328
[3813510.574965] BTRFS warning (device sdd): csum failed root 5 ino
44197278 off 288227328 csum 0xa0775535 expected csum 0x00000000 mirror
3
[3813510.574980] BTRFS info (device sdd): no csum found for inode
44197278 start 288227328
[3813510.576050] BTRFS warning (device sdd): csum failed root 5 ino
44197278 off 288227328 csum 0xa0775535 expected csum 0x00000000 mirror
4
[3813510.576070] BTRFS info (device sdd): no csum found for inode
44197278 start 288227328
[3813510.577198] BTRFS warning (device sdd): csum failed root 5 ino
44197278 off 288227328 csum 0xa0775535 expected csum 0x00000000 mirror
5
[3813510.577214] BTRFS info (device sdd): no csum found for inode
44197278 start 288227328
[3813510.578222] BTRFS warning (device sdd): csum failed root 5 ino
44197278 off 288227328 csum 0xa0775535 expected csum 0x00000000 mirror
6

             reply	other threads:[~2020-07-14 16:14 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-14 16:13 John Petrini [this message]
2020-07-15  1:18 ` Filesystem Went Read Only During Raid-10 to Raid-6 Data Conversion Zygo Blaxell
     [not found]   ` <CADvYWxcq+-Fg0W9dmc-shwszF-7sX+GDVig0GncpvwKUDPfT7g@mail.gmail.com>
     [not found]     ` <20200716042739.GB8346@hungrycats.org>
2020-07-16 13:37       ` John Petrini
     [not found]         ` <CAJix6J9kmQjfFJJ1GwWXsX7WW6QKxPqpKx86g7hgA4PfbH5Rpg@mail.gmail.com>
2020-07-16 22:57           ` Zygo Blaxell
2020-07-17  1:11             ` John Petrini
2020-07-17  5:57               ` Zygo Blaxell
2020-07-17 22:54                 ` John Petrini
2020-07-18 10:36                 ` Steven Davies
2020-07-20 17:57                   ` Goffredo Baroncelli
2020-07-21 10:15                     ` Steven Davies
2020-07-21 20:48                       ` Goffredo Baroncelli
2020-07-23  8:57                         ` Steven Davies
2020-07-23 19:29                           ` Zygo Blaxell

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=CADvYWxeiNynEWUYwfQxP7fQTK4k2Q+eDZsA8j7rLcaTSeND9fg@mail.gmail.com \
    --to=john.d.petrini@gmail.com \
    --cc=linux-btrfs@vger.kernel.org \
    /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.