From: "Niels de Carpentier" <niels@decarpentier.com>
To: "Vincent Vanackere" <vincent.vanackere@gmail.com>
Cc: linux-btrfs@vger.kernel.org,
"Vincent Vanackere" <vincent.vanackere@gmail.com>
Subject: Re: btrfs-related kernel oops due to media error
Date: Tue, 10 Jan 2012 00:01:31 +0100 [thread overview]
Message-ID: <40bebf953d60c05eff25fbde5bfbef17.squirrel@webmail.decarpentier.com> (raw)
In-Reply-To: <4F0B6BCB.80308@gmail.com>
> Hi,
>
> One of my disks, partitioned into a single btrfs partition, is showing
> media errors. The problem is that these errors lead to kernel panic from
> btrfs - that make the filesystem unusable until reboot - and therefore
> it is very hard for me to do a full backup of the data prior to changing
> the disk.
> My current kernel is 3.2.0-8-generic from Ubuntu/precise (based on linux
> 3.2-final) but I quickly tested and get the same error with an older 3.1
> kernel (and I can probably reproduce it with a vanilla kernel if
> necessary).
> I assume that the filesystem should not panic even in case of a media
> error... Is there any procedure I can follow / patch I could apply to
> salvage my data while ignoring media errors ?
I don't know about btrfs, but writing the sector with hdparm
--write-sector will usually cause it to be remapped. You can use dd or
another tool to read the entire disk to find out if there are more bad
sectors.
Niels
next prev parent reply other threads:[~2012-01-09 23:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-09 22:35 btrfs-related kernel oops due to media error Vincent Vanackere
2012-01-09 23:01 ` Niels de Carpentier [this message]
2012-01-12 22:39 ` Vincent Vanackere
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=40bebf953d60c05eff25fbde5bfbef17.squirrel@webmail.decarpentier.com \
--to=niels@decarpentier.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=vincent.vanackere@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).