From: "Ken D'Ambrosio" <ken@jots.org>
To: linux-btrfs@vger.kernel.org,
"René Vangsgaard" <rene.vangsgaard@gmail.com>
Subject: Re: mount errors
Date: Mon, 21 Nov 2011 11:27:24 -0500 [thread overview]
Message-ID: <ad43919226351cd8f695a0dfc44adc81@www.jots.org> (raw)
In-Reply-To: <CAPWZyXa84avAjPfsv0FS8L67+uWSk0LKj7pUvLT3JM+bE4wwag@mail.gmail.com>
1) As of right now, btrfs's fsck is "done when it's done." So don't ho=
ld your
breath, I'm afraid.
2) What errors do you get on mount? It may be as simple as changing yo=
ur fstab
entry such that fsck isn't attempted to be run. (Change the last colum=
n to
"0".) =20
-Ken
On Sat, 19 Nov 2011 14:01:41 +0100 Ren=C3=A9 Vangsgaard <rene.vangsgaar=
d@gmail.com>
wrote
> Hi - I have been using btrfs on /home for 2 weeks, and now it mounts
> with errors. I know that no fsck is available yet. I ignore the error
> and it still works, for now. Can I do anything to help you debug this
> problem with btrfs?
> Any news on fsck for btrfs?
>=20
> I am running Ubuntu 11.10.
> Thank you, Ren=C3=A9
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs=
" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-11-21 16:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-19 13:01 mount errors René Vangsgaard
2011-11-21 16:27 ` Ken D'Ambrosio [this message]
2011-11-21 23:29 ` René Vangsgaard
2011-11-22 4:55 ` cwillu
2011-11-22 13:01 ` René Vangsgaard
2011-11-22 13:06 ` cwillu
2011-11-22 13:26 ` René Vangsgaard
2011-11-22 13:56 ` Jan Schmidt
2011-11-22 14:24 ` René Vangsgaard
2011-11-24 23:04 ` René Vangsgaard
2011-11-21 23:32 ` René Vangsgaard
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=ad43919226351cd8f695a0dfc44adc81@www.jots.org \
--to=ken@jots.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=rene.vangsgaard@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).