linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hugo Mills <hugo@carfax.org.uk>
To: cwillu <cwillu@cwillu.com>
Cc: Tommy Faasen <tommy@zwanebloem.nl>, linux-btrfs@vger.kernel.org
Subject: Re: Btrfs out of inodes becomes corrupt
Date: Mon, 6 Feb 2012 11:40:31 +0000	[thread overview]
Message-ID: <20120206114031.GD19330@carfax.org.uk> (raw)
In-Reply-To: <CAE5mzvhwSLqBEMEOZo8Xxx63LciYLAxYWzVrQP+7qk_tgyRvwA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 697 bytes --]

On Mon, Feb 06, 2012 at 05:33:51AM -0600, cwillu wrote:
> >  3.0 is two revisions old -- something on the order of 6
> > months. There's been a lot of development since then, too. You really
> > should be running 3.2 or 3.2-rc2 (i.e. the latest released or latest
> > development version of the kernel).
> 
> I think you meant 3.2 or 3.3-rc2.

   I did indeed. Thanks for the correction.

   Hugo.

-- 
=== Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk ===
  PGP key: 515C238D from wwwkeys.eu.pgp.net or http://www.carfax.org.uk
  --- "What's so bad about being drunk?" "You ask a glass of water" ---  
                                                                         

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 190 bytes --]

  reply	other threads:[~2012-02-06 11:40 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 [this message]
2012-02-06 15:35       ` Tommy Faasen
2012-02-08 11:13         ` Hugo Mills
2012-02-08  6:41   ` Chris Samuel
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=20120206114031.GD19330@carfax.org.uk \
    --to=hugo@carfax.org.uk \
    --cc=cwillu@cwillu.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=tommy@zwanebloem.nl \
    /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).