From: Zach Brown <zab@zabbo.net>
To: "Hugo Mills" <hugo@carfax.org.uk>,
"Swâmi Petaramesh" <swami@petaramesh.org>,
linux-btrfs@vger.kernel.org
Subject: Re: BTRFS fsck apparent errors
Date: Tue, 03 Jul 2012 10:42:10 -0700 [thread overview]
Message-ID: <4FF32EF2.2090403@zabbo.net> (raw)
In-Reply-To: <20120703173742.GH5326@twin.jikos.cz>
> read-only mode is default and (hopefully) does no writes to the device,
> this would require the --repair option so what you propose is sort of a
> sanity check, right?
Ah, I didn't realize that it didn't write without --repair. Yeah,
making sure that people don't try to combine the repair and
read-from-mounted-devices options seems reasonable.
- z
next prev parent reply other threads:[~2012-07-03 17:42 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 [this message]
2012-07-04 3:25 ` Dave Chinner
2012-07-03 19:17 ` Swâmi Petaramesh
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=4FF32EF2.2090403@zabbo.net \
--to=zab@zabbo.net \
--cc=hugo@carfax.org.uk \
--cc=linux-btrfs@vger.kernel.org \
--cc=swami@petaramesh.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