On May 6, 2011 4:20 PM, <cac...@quantum-sci.com> wrote:
>
> On Friday 6 May, 2011 13:51:37 Peter Stuge wrote:
> > cac...@quantum-sci.com wrote:
> > > I don't understand this.
> >
> > Clearly. Please continue the discussion in a debian or grub forum..
> > It really has nothing to do with btrfs.
>
> No thanks.  This is a BTRFS problem, and if you people don't want to face it, 
> that's fine.
>
> I'm tearing out BTRFS and using another filesystem.  And rest assured, I'm 
> warning others too.
>
> That's enough.

hm.  well to anyone who stumbles across this thread in the future,
i've managed to use btrfs as my root on 1-3+ machines since circa
2.6.32, possibly even earlier (albeit not on Debian -- Archlinux
w00tw00t ;-) ...

... there have certainly been a few bumps along the way, but not
_once_ at the fault of btrfs ... not ONCE.  tbh, I personally KNOW the
developers and community here are doing one hell of a job -- i've been
on this list almost 3 years i think, and along the way everyone has
been most helpful + accommodating; i mean i've seen Chris and others
extending rather gracious support levels when helping users recover
data or debug issues ... and considering the demand/anticipation
surrounding btrfs, this list is relatively devoid of support issues --
it's easily one of the highest quality groups i frequent.

in short, distro's only just recently began offering btrfs at install
time, with a big *warning sticker* on it.  as others have already
stated, this is clearly a Debian-specific problem, and does not
reflect negatively on btrfs whatsoever, which has been nothing short
of spectacular since the day i tried it and very much exactly as
advertised -- i haven't used anything else since (save my servers
...).

i am sorry you've found yourself in this position, i really am, as
i've been there myself, but please do try and acknowledge the
considerations already extended your way -- my post marks the 51st
message in this thread.

C Anthony
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to