All of lore.kernel.org
 help / color / mirror / Atom feed
From: Josef Bacik <jbacik@fusionio.com>
To: "Swâmi Petaramesh" <swami@petaramesh.org>
Cc: Josef Bacik <JBacik@fusionio.com>,
	Linux Btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: "free space cache generation" ?
Date: Wed, 19 Sep 2012 14:02:24 -0400	[thread overview]
Message-ID: <20120919180224.GE2272@localhost.localdomain> (raw)
In-Reply-To: <505A06DE.1050503@petaramesh.org>

On Wed, Sep 19, 2012 at 11:54:38AM -0600, Swâmi Petaramesh wrote:
> Le 19/09/2012 19:36, Josef Bacik a écrit :
> > It can happen for all sorts of different reasons. Did you have a
> > unclean unmount at some point?
> 
> Not that I'm aware of...
> 
> > Do you have a particularly full file system?
> 
> ~1 TB FS, 23% full...
> 
> Only, I have several Linux distros installed on the same BTRFS  - in
> different subvols - so I sometimes mount it with a 3.5.x kernel, and
> more rarely - but sometimes - with a 3.2.x...
> 

Well I think I changed the space cache format between those releases which would
cause them all to be discarded and remade.

> => Also I have to mention that I have lost a complete BTRFS FS, that was
> a /boot with snapshots. At some point it started to fail mounting, the
> kernel complaining that some trees (corresponding to removed snapshots
> as far as I could tell) were b0rked, and btrfsck couldn't help...
> 
> So I lost the FS - and lost quite a bit of confidence into BTRFS the
> same day... :-\
> 

Yes well, welcome to using an experimental file system.

Josef

      reply	other threads:[~2012-09-19 18:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-19  8:05 "free space cache generation" ? Swâmi Petaramesh
2012-09-19 16:01 ` Josef Bacik
2012-09-19 17:30   ` Swâmi Petaramesh
2012-09-19 17:36     ` Josef Bacik
2012-09-19 17:54       ` Swâmi Petaramesh
2012-09-19 18:02         ` Josef Bacik [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=20120919180224.GE2272@localhost.localdomain \
    --to=jbacik@fusionio.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=swami@petaramesh.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.