From: Chris Mason <chris.mason@oracle.com>
To: Leonidas Spyropoulos <artafinde@gmail.com>
Cc: cwillu <cwillu@cwillu.com>, linux-btrfs@vger.kernel.org
Subject: Re: btrfs filesystem df not working
Date: Thu, 14 Oct 2010 12:42:30 -0400 [thread overview]
Message-ID: <20101014164230.GX22691@think> (raw)
In-Reply-To: <AANLkTimRTycuHq6aWir=ZJUAHKc1rb6QXteLG7sMN6ge@mail.gmail.com>
On Thu, Oct 14, 2010 at 12:45:59PM +0100, Leonidas Spyropoulos wrote:
> On Wed, Oct 13, 2010 at 4:08 PM, Chris Mason <chris.mason@oracle.com>=
wrote:
> > On Wed, Oct 13, 2010 at 10:52:57AM +0100, Leonidas Spyropoulos wrot=
e:
> >> On Wed, Oct 13, 2010 at 1:43 AM, Chris Mason <chris.mason@oracle.c=
om> wrote:
> >> > On Tue, Oct 12, 2010 at 02:45:19PM +0100, Leonidas Spyropoulos w=
rote:
> >> >> On Tue, Oct 12, 2010 at 2:43 PM, cwillu <cwillu@cwillu.com> wro=
te:
> >> >> > On Tue, Oct 12, 2010 at 4:12 AM, Leonidas Spyropoulos
> >> >> > <artafinde@gmail.com> wrote:
> >> >> >> The above command is not working on my system.
> >> >> >> Information:
> >> >> >> btrfs f df /media/data
> >> >> >
> >> >> > btrfs f isn't unique; =A0fi is the minimum to specify "filesy=
stem"
> >> >> >
> >> >> I tried even with btrfs filesystem df /media/data
> >> >> and same results.
> >> >
> >> > Does strace give us any clues?
> >> >
> >> According to strace there is inappropriate ioctl for the device.
> >> Here is the log
> >
> > I missed this before:
> >
> > 2.6.32-5-amd64
> >
> > The df ioctl was added after 2.6.32 (2.6.33 I think).
>=20
> So in debian squeeze/unstable which is currently on 2.6.32 (and won't
> change any sooner) I cannot use btrfs. All I can do is try
> experimental kernels?
Or backport the changes, yes.
> 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?
We haven't made any of those changes, you'll be fine going back and
forth.
-chris
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-10-14 16:42 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
2010-10-14 16:42 ` Chris Mason [this message]
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=20101014164230.GX22691@think \
--to=chris.mason@oracle.com \
--cc=artafinde@gmail.com \
--cc=cwillu@cwillu.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).