From: Felix Blanke <felixblanke@gmail.com>
To: helmut@hullen.de
Cc: Helmut Hullen <Hullen@t-online.de>, linux-btrfs@vger.kernel.org
Subject: Re: Kernel Modules
Date: Sun, 10 Jul 2011 02:56:28 -0400 [thread overview]
Message-ID: <4E194D1C.9060707@gmail.com> (raw)
In-Reply-To: <BpWht+my1uB@helmut.hullen.de>
Did you ever say something positive about btrfs? :D All I read from in
the last months is complaining about btrfs.
In this case it was his fault because he forget to update the fstab. Im
pretty sure it was also your fault when you screwed up your 2.6.38.5
kernel...
I'm sorry but it seems that 90% for your comments are useless and they
sound like you only want to say something bad about btrfs.
Regards,
Felix
On 7/9/11 1:33 PM, Helmut Hullen wrote:
> Hallo, Cacook,
>
> Du meintest am 09.07.11:
>
>> Just compiled a custom kernel, but unable to mount a btrfs partition.
>> It essentially says 'unrecognized filesystem'. What could be
>> missing?
>
> Perhaps you only need a newer kernel. Sounds funny, but some days ago I
> had a similar problem, with kernel 2.6.38.5
>
> Then I compiled kernel 2.6.39.2 - all worked as well as (about) a week
> ago.
>
> Maybe I can't reproduce this behaviour, but I don't want to see it again
> - restoring more than 4 TByte is no fun.
>
> Viele Gruesse!
> Helmut
> --
> 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-07-10 6:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-09 16:19 Kernel Modules CACook
2011-07-09 17:12 ` Andreas Philipp
2011-07-09 17:28 ` CACook
2011-07-09 17:39 ` Hugo Mills
2011-07-10 8:24 ` Goffredo Baroncelli
2011-07-09 17:33 ` Helmut Hullen
2011-07-10 6:56 ` Felix Blanke [this message]
2011-07-10 7:29 ` Helmut Hullen
2011-07-10 14:24 ` Felix Blanke
2011-07-10 15:57 ` Helmut Hullen
2011-07-10 16:42 ` Felix Blanke
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=4E194D1C.9060707@gmail.com \
--to=felixblanke@gmail.com \
--cc=Hullen@t-online.de \
--cc=helmut@hullen.de \
--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).