btrfs filesystem df not working

btrfs filesystem df not working

[Leonidas Spyropoulos]

The above command is not working on my system.
Information:
btrfs f df /media/data

Btrfs v0.19-35-g1b444cd

Linux woofy 2.6.32-5-amd64 #1 SMP Fri Sep 17 21:50:19 UTC 2010 x86_64 GNU/Linux

mount info:
/dev/sdd2 on /media/data type btrfs (rw,noexec,nosuid,nodev)
/media/data is a raid 0 filesystem

$ btrfs filesystem show
failed to read /dev/sr0
Label: none  uuid: 1882b025-58e4-4287-98a3-9b772af0ad76
	Total devices 2 FS bytes used 72.56GB
	devid    2 size 74.53GB used 54.01GB path /dev/sdd2
	devid    3 size 74.53GB used 54.01GB path /dev/sde2

Any ideas?
This is on an testing/unstable Debian system.

-- 
Caution: breathing may be hazardous to your health.

Re: btrfs filesystem df not working

[Leonidas Spyropoulos]

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 "filesystem"
>
I tried even with btrfs filesystem df /media/data
and same results.


--=20
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  http://vger.kernel.org/majordomo-info.html

Re: btrfs filesystem df not working

[Chris Mason]

On Tue, Oct 12, 2010 at 02:45:19PM +0100, Leonidas Spyropoulos 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 "filesystem"
> >
> I tried even with btrfs filesystem df /media/data
> and same results.

Does strace give us any clues?

-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

Re: btrfs filesystem df not working

[Leonidas Spyropoulos]

On Wed, Oct 13, 2010 at 1:43 AM, Chris Mason <chris.mason@oracle.com> w=
rote:
> On Tue, Oct 12, 2010 at 02:45:19PM +0100, Leonidas Spyropoulos 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 "filesystem"
>> >
>> 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

PS: results are the same for root access

[inglor@woofy ~]$ strace btrfs filesystem df /media/data/
execve("/usr/local/bin/btrfs", ["btrfs", "filesystem", "df",
"/media/data/"], [/* 16 vars */]) =3D 0
brk(0)                                  =3D 0x11ed000
access("/etc/ld.so.nohwcap", F_OK)      =3D -1 ENOENT (No such file or =
directory)
mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) =3D 0x7fd28d424000
access("/etc/ld.so.preload", R_OK)      =3D -1 ENOENT (No such file or =
directory)
open("/etc/ld.so.cache", O_RDONLY)      =3D 3
fstat(3, {st_mode=3DS_IFREG|0644, st_size=3D126024, ...}) =3D 0
mmap(NULL, 126024, PROT_READ, MAP_PRIVATE, 3, 0) =3D 0x7fd28d405000
close(3)                                =3D 0
access("/etc/ld.so.nohwcap", F_OK)      =3D -1 ENOENT (No such file or =
directory)
open("/lib/libuuid.so.1", O_RDONLY)     =3D 3
read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\360\25\0\0\0\0\=
0\0"...,
832) =3D 832
fstat(3, {st_mode=3DS_IFREG|0644, st_size=3D15720, ...}) =3D 0
mmap(NULL, 2110736, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3,
0) =3D 0x7fd28d005000
mprotect(0x7fd28d009000, 2093056, PROT_NONE) =3D 0
mmap(0x7fd28d208000, 4096, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x3000) =3D 0x7fd28d208000
close(3)                                =3D 0
access("/etc/ld.so.nohwcap", F_OK)      =3D -1 ENOENT (No such file or =
directory)
open("/lib/libc.so.6", O_RDONLY)        =3D 3
read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0`\355\1\0\0\0\0\=
0"...,
832) =3D 832
fstat(3, {st_mode=3DS_IFREG|0755, st_size=3D1432968, ...}) =3D 0
mmap(NULL, 3541032, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3,
0) =3D 0x7fd28cca4000
mprotect(0x7fd28cdfc000, 2093056, PROT_NONE) =3D 0
mmap(0x7fd28cffb000, 20480, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x157000) =3D 0x7fd28cffb000
mmap(0x7fd28d000000, 18472, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) =3D 0x7fd28d000000
close(3)                                =3D 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) =3D 0x7fd28d404000
mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) =3D 0x7fd28d402000
arch_prctl(ARCH_SET_FS, 0x7fd28d402740) =3D 0
mprotect(0x7fd28cffb000, 16384, PROT_READ) =3D 0
mprotect(0x7fd28d426000, 4096, PROT_READ) =3D 0
munmap(0x7fd28d405000, 126024)          =3D 0
brk(0)                                  =3D 0x11ed000
brk(0x120e000)                          =3D 0x120e000
stat("/media/data/", {st_mode=3DS_IFDIR|0755, st_size=3D124, ...}) =3D =
0
open("/media/data/", O_RDONLY|O_NONBLOCK|O_DIRECTORY|O_CLOEXEC) =3D 3
fcntl(3, F_GETFD)                       =3D 0x1 (flags FD_CLOEXEC)
ioctl(3, 0xc0109414, 0x11f5620)         =3D -1 ENOTTY (Inappropriate
ioctl for device)


> -chris
>
>



--=20
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  http://vger.kernel.org/majordomo-info.html

Re: btrfs filesystem df not working

[Chris Mason]

On Wed, Oct 13, 2010 at 10:52:57AM +0100, Leonidas Spyropoulos wrote:
> On Wed, Oct 13, 2010 at 1:43 AM, Chris Mason <chris.mason@oracle.com>=
 wrote:
> > On Tue, Oct 12, 2010 at 02:45:19PM +0100, Leonidas Spyropoulos wrot=
e:
> >> 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 "filesyste=
m"
> >> >
> >> 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).

-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

Re: btrfs filesystem df not working

[Leonidas Spyropoulos]

On Wed, Oct 13, 2010 at 4:08 PM, Chris Mason <chris.mason@oracle.com> w=
rote:
> On Wed, Oct 13, 2010 at 10:52:57AM +0100, Leonidas Spyropoulos wrote:
>> On Wed, Oct 13, 2010 at 1:43 AM, Chris Mason <chris.mason@oracle.com=
> wrote:
>> > On Tue, Oct 12, 2010 at 02:45:19PM +0100, Leonidas Spyropoulos wro=
te:
>> >> 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 "filesyst=
em"
>> >> >
>> >> 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).

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?
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?

>
> -chris
>



--=20
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  http://vger.kernel.org/majordomo-info.html

Re: btrfs filesystem df not working

[David Nicol]

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)

Re: btrfs filesystem df not working

[Chris Mason]

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

Re: btrfs filesystem df not working

[Leonidas Spyropoulos]

On Thu, Oct 14, 2010 at 5:42 PM, Chris Mason <chris.mason@oracle.com> w=
rote:
> 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 wro=
te:
>> >> On Wed, Oct 13, 2010 at 1:43 AM, Chris Mason <chris.mason@oracle.=
com> wrote:
>> >> > On Tue, Oct 12, 2010 at 02:45:19PM +0100, Leonidas Spyropoulos =
wrote:
>> >> >> On Tue, Oct 12, 2010 at 2:43 PM, cwillu <cwillu@cwillu.com> wr=
ote:
>> >> >> > 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 "files=
ystem"
>> >> >> >
>> >> >> 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).
>>
>> 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.
Sorry, I don't understand what "backport the changes" means?

>
>> 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 ol=
d
>> ones cannot read?
>
> We haven't made any of those changes, you'll be fine going back and
> forth.
>
> -chris
>



--=20
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  http://vger.kernel.org/majordomo-info.html

Re: btrfs filesystem df not working

[Chester]

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

Re: btrfs filesystem df not working

[Chris Samuel]

[-- Attachment #1: Type: Text/Plain, Size: 921 bytes --]

On Sun, 17 Oct 2010 12:46:14 am Leonidas Spyropoulos wrote:

> Sorry, I don't understand what "backport the changes" means?

Chris means that you can take the changes that have gone into
the btrfs code since 2.6.32 and try and port them back to the
old 2.6.32 kernel code.  It's a non-trivial task.

Luckily for you Mitch Harder posted a message called "Backporting
Recent Btrfs Patches to 2.6.32" yesterday where he described his
attempts to do just that, he has a git repository for the resulting
kernel here:

http://gitweb.sabayon.org/?p=linux/kernel/btrfs-backport.git;a=summary

You can find Mitch's original message here:

http://permalink.gmane.org/gmane.comp.file-systems.btrfs/7102

cheers,
Chris
-- 
 Chris Samuel  :  http://www.csamuel.org/  :  Melbourne, VIC

This email may come with a PGP signature as a file. Do not panic.
For more info see: http://en.wikipedia.org/wiki/OpenPGP

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 482 bytes --]