From: Liam <liam.bulkley@gmail.com>
To: cwillu <cwillu@cwillu.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: kernel oops -> no mount (different problem than others)
Date: Sat, 20 Aug 2011 01:53:39 -0400 [thread overview]
Message-ID: <CAO2p3yFyDUAA9PjaGRdTfDia7G_RsxGf8F_BECpaDP1ibk3UTQ@mail.gmail.com> (raw)
In-Reply-To: <CAE5mzvg9Yd2qSrpSqKTNmu08z83JmgYtGZmuLg6aYGLMei26AQ@mail.gmail.com>
Thanks for your help, but unfortunately, it wouldn't mount read-only,
either. If you can think of anything else I could try, it would be
greatly appreciated! Thanks!
- Liam
On Thu, Aug 18, 2011 at 8:52 PM, cwillu <cwillu@cwillu.com> wrote:
> You might try mounting it "-o ro" as a stopgap to regain readonly acc=
ess.
>
> Judging from the bootlog, the error itself appears to be enospc. =A0I=
n
> which case there's no already-available quick fix; I expect a
> developer to chime in any second now :p
>
>> From the logs it is listing a transid error but NOT that it is
>> expecting a different one, simply
>>
>> device label 1TB devid 1 transid 248472 /dev/sdb
>
> That particular line is the normal listing of devices, which is
> expected and completely normal.
>
--
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
prev parent reply other threads:[~2011-08-20 5:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-19 0:40 kernel oops -> no mount (different problem than others) Liam
2011-08-19 0:52 ` cwillu
2011-08-20 5:53 ` Liam [this message]
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=CAO2p3yFyDUAA9PjaGRdTfDia7G_RsxGf8F_BECpaDP1ibk3UTQ@mail.gmail.com \
--to=liam.bulkley@gmail.com \
--cc=cwillu@cwillu.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 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).