Re: btrfs filesystem df not working

[Chester <somethingsome2000@gmail.com>]

I think that means that the fixes in the newer versions will also be
included in the previous versions.

On Sat, Oct 16, 2010 at 8:46 AM, Leonidas Spyropoulos
<artafinde@gmail.com> wrote:
>
> On Thu, Oct 14, 2010 at 5:42 PM, Chris Mason <chris.mason@oracle.com>=
 wrote:
> > On Thu, Oct 14, 2010 at 12:45:59PM +0100, Leonidas Spyropoulos wrot=
e:
> >> On Wed, Oct 13, 2010 at 4:08 PM, Chris Mason <chris.mason@oracle.c=
om> wrote:
> >> > On Wed, Oct 13, 2010 at 10:52:57AM +0100, Leonidas Spyropoulos w=
rote:
> >> >> On Wed, Oct 13, 2010 at 1:43 AM, Chris Mason <chris.mason@oracl=
e.com> wrote:
> >> >> > On Tue, Oct 12, 2010 at 02:45:19PM +0100, Leonidas Spyropoulo=
s wrote:
> >> >> >> On Tue, Oct 12, 2010 at 2:43 PM, cwillu <cwillu@cwillu.com> =
wrote:
> >> >> >> > 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 "fil=
esystem"
> >> >> >> >
> >> >> >> 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=
=2E
> >> >> 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).
> >>
> >> So in debian squeeze/unstable which is currently on 2.6.32 (and wo=
n't
> >> change any sooner) I cannot use btrfs. All I can do is try
> >> experimental kernels?
> >
> > Or backport the changes, yes.
> Sorry, I don't understand what "backport the changes" means?
>
> >
> >> My question though is, if I use experimental kernels can I then lo=
ad
> >> 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
> >
>
>
>
> --
> Caution: breathing may be hazardous to your health.
> --
> 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 =A0http://vger.kernel.org/majordomo-info.html
--
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