All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ashu Tiwary <ashuatibm@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: Corruption on Big Endian System
Date: Mon, 26 Mar 2018 10:00:04 -0500	[thread overview]
Message-ID: <CACJ+inTx=1tfrx0V-2gwq08xxMxvzCq7oBPGcPnH8xUhtX4uBQ@mail.gmail.com> (raw)

It appears my system may have hit the issue reverted here (
https://www.mail-archive.com/linux-btrfs@vger.kernel.org/msg74621.html
) ( [PATCH] Revert "btrfs: use proper endianness accessors for
super_copy" ); system is an IBM OpenPower 720 (Big Endian) running
Fedora 27; kernel was at 4.15.9; attempting to reboot after updating
system (including kernel to 4.15.10) caused system to not be able to
boot:

=====
         Mounting /sysroot...
[   34.644721] BTRFS warning (device dm-3): suspicious: generation <
chunk_root_generation: 15959351903540740096 < 17261735521269317632
[   34.644761] BTRFS info (device dm-3): disk space caching is enabled
[   34.644771] BTRFS info (device dm-3): has skinny extents
[   34.645925] BTRFS critical (device dm-3): unable to find logical
71472550772736 length 65536
[   34.645941] BTRFS critical (device dm-3): unable to find logical
71472550772736 length 65536
[   34.645952] BTRFS error (device dm-3): failed to read chunk root
[   34.807156] BTRFS error (device dm-3): open_ctree failed
[FAILED] Failed to mount /sysroot.
=====

It appears there is a manual method available to repair the corrupted
superblock: can that be made available?

Thanks,

-Ashu

--
Ashu Tiwary
ashuatibm@gmail.com

             reply	other threads:[~2018-03-26 15:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-26 15:00 Ashu Tiwary [this message]
2018-03-27  3:45 ` Corruption on Big Endian System Anand Jain
2018-03-27 12:13 ` David Sterba
2018-03-29  3:27   ` Ashu Tiwary

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='CACJ+inTx=1tfrx0V-2gwq08xxMxvzCq7oBPGcPnH8xUhtX4uBQ@mail.gmail.com' \
    --to=ashuatibm@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.