From: "Swâmi Petaramesh" <swami@petaramesh.org>
To: Hugo Mills <hugo@carfax.org.uk>, linux-btrfs@vger.kernel.org
Subject: Re: BTRFS fsck apparent errors
Date: Tue, 03 Jul 2012 21:17:19 +0200 [thread overview]
Message-ID: <4FF3453F.5090404@petaramesh.org> (raw)
In-Reply-To: <20120703152208.GA28701@carfax.org.uk>
Le 03/07/2012 17:22, Hugo Mills a écrit :
> What you're seeing is the fact that you've still got the complete ext4
> filesystem and all of its data sitting untouched on the disk as well.
> The defrag will have taken a complete new copy of the data but not
> removed the ext4 copy.
I though about that... However, I had "btrfs su del" the ext2_saved
subvolume, so it is expected to have been deleted...
If not, how could I possibly delete it, now that I can't see it anymore ?
>> It doesn't seem that btrfsck attempts to fix these errors in any
>> way... It just displays them.
> Correct, by default it just checks the filesystem. Just to be sure:
> the filesystems in question weren't mounted, were they?
>
>
No, the filesystems weren't mounted... If by default, btrfsck doesn't
fix, how could I ask it to fix ? "man btrfsck" or "btrfsck -h" do not
show any option, only a device name...
TIA.
Kind regards.
--
Swâmi Petaramesh <swami@petaramesh.org> http://petaramesh.org PGP 9076E32E
next prev parent reply other threads:[~2012-07-03 19:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-03 15:10 BTRFS fsck apparent errors Swâmi Petaramesh
2012-07-03 15:22 ` Hugo Mills
2012-07-03 15:52 ` David Sterba
2012-07-03 16:26 ` Zach Brown
2012-07-03 17:37 ` David Sterba
2012-07-03 17:42 ` Zach Brown
2012-07-04 3:25 ` Dave Chinner
2012-07-03 19:17 ` Swâmi Petaramesh [this message]
2012-07-04 0:40 ` Fajar A. Nugraha
2012-07-04 13:42 ` David Sterba
2012-07-04 15:46 ` Fajar A. Nugraha
2012-07-05 0:32 ` David Sterba
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=4FF3453F.5090404@petaramesh.org \
--to=swami@petaramesh.org \
--cc=hugo@carfax.org.uk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox