linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris Samuel <chris@csamuel.org>
To: linux-btrfs@vger.kernel.org
Subject: Re: Btrfs out of inodes becomes corrupt
Date: Wed, 8 Feb 2012 17:41:12 +1100	[thread overview]
Message-ID: <201202081741.13243.chris@csamuel.org> (raw)
In-Reply-To: <20120205195742.GC19330@carfax.org.uk>

[-- Attachment #1: Type: Text/Plain, Size: 1274 bytes --]

On Monday 06 February 2012 06:57:42 Hugo Mills wrote:

> > This al under debian  with kernel 2.6.32-5.
> 
>    Aargh.
> 
>    You are aware that this is an insanely old version of the brtfs
> code, and it has major flaws in it?

As someone who runs his work laptop with a 2.6.32 laptop and btrfs for 
/home I'll bite at this one - I've held off updating after reading the 
issues people were reporting on the list with newer kernels that did 
not appear to be present in 2.6.32 (indeed IIRC a particular problem 
from that time could only be solved at the time be remounting the 
filesystem with 2.6.32, at which point newer kernels could access it 
again).   It's served me very well, it "just works" (so far at least).

It's now sounding that 3.2 is probably stable enough for me to 
consider updating to the next KUbuntu release when it comes out.

NB:  Yes, I do make nightly backups, and no, I don't run the 
filesystem at anything close to even a quarter full (not that that 
guarantees anything, or is even particularly deliberate).

cheers,
Chris
-- 
 Chris Samuel  :  http://www.csamuel.org/  :  Melbourne, VIC

This email may come with a PGP signature as a file. Do not panic.
For more info see: http://en.wikipedia.org/wiki/OpenPGP

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 482 bytes --]

  parent reply	other threads:[~2012-02-08  6:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-05 19:18 Btrfs out of inodes becomes corrupt Tommy Faasen
2012-02-05 19:57 ` Hugo Mills
2012-02-06 11:33   ` cwillu
2012-02-06 11:40     ` Hugo Mills
2012-02-06 15:35       ` Tommy Faasen
2012-02-08 11:13         ` Hugo Mills
2012-02-08  6:41   ` Chris Samuel [this message]
2012-02-08  9:00     ` 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=201202081741.13243.chris@csamuel.org \
    --to=chris@csamuel.org \
    --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).