linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Nicol <davidnicol@gmail.com>
To: Leonidas Spyropoulos <artafinde@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: btrfs filesystem df not working
Date: Thu, 14 Oct 2010 11:06:55 -0500	[thread overview]
Message-ID: <AANLkTi=J67ZWz31UwWEccNHA+QL-7EB9WZtUqVYS75XD@mail.gmail.com> (raw)
In-Reply-To: <AANLkTimRTycuHq6aWir=ZJUAHKc1rb6QXteLG7sMN6ge@mail.gmail.com>

On Thu, Oct 14, 2010 at 6:45 AM, Leonidas Spyropoulos
<artafinde@gmail.com> wrote:

> My question though is, if I use experimental kernels can I then load
> an "old" kernel and still use the btrfs filesystem?
> Or the newer kernels write anything specials on ionodes which the old
> ones cannot read?

My understanding is that what you have just described is the point of
"freezing the on-disk format" and that the on-disk format is frozen.

I hope someone will correct me if this is wrong.

If a filesystem revision uses something different for the i-node
number as presented to the VFS, therefore, it would have to do that
without affecting the on-disk format. (considering trying to allow
symlinks over subvolume boundaries, or at least better understand the
cases necessitating their prohibition)

Also, the system xattr name space might get different things written
to it for new experimental features besides access control, but
existence of this additional metadata would not affect readability by
an older system, unless the metadata in question was for instance an
encryption key. (just made that up as an example, not working on
anything like that)

  reply	other threads:[~2010-10-14 16:06 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-12 10:12 btrfs filesystem df not working Leonidas Spyropoulos
     [not found] ` <AANLkTi=1VgjsZoJqzkp-zto3vAMUThh7TN054xQ1mpEu@mail.gmail.com>
2010-10-12 13:45   ` Leonidas Spyropoulos
2010-10-13  0:43     ` Chris Mason
2010-10-13  9:52       ` Leonidas Spyropoulos
2010-10-13 15:08         ` Chris Mason
2010-10-14 11:45           ` Leonidas Spyropoulos
2010-10-14 16:06             ` David Nicol [this message]
2010-10-14 16:42             ` Chris Mason
2010-10-16 13:46               ` Leonidas Spyropoulos
2010-10-16 15:40                 ` Chester
2010-10-16 23:13                 ` Chris Samuel

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='AANLkTi=J67ZWz31UwWEccNHA+QL-7EB9WZtUqVYS75XD@mail.gmail.com' \
    --to=davidnicol@gmail.com \
    --cc=artafinde@gmail.com \
    --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).