Hallo, linux-btrfs,
I''ve just compiled kernel 3.9.04 and run
btrfs filesystem show
On my system (Slackware 13.37, self made, without "udev") it still
shows
a lot of non existent devices (I have shortened the list ...):
# btrfs fi show
failed to read /dev/hdb4
failed to read /dev/scd9
failed to read /dev/hda6
failed to read /dev/hda
failed to read /dev/sde
failed to read /dev/hdd3
failed to read /dev/sdl6
failed to read /dev/hdc9
failed to read /dev/sdg9
failed to read /dev/lmscd
failed to read /dev/scd1
failed to read /dev/hdd7
failed to read /dev/sdj6
failed to read /dev/scd5
failed to read /dev/sdg3
failed to read /dev/sda5
failed to read /dev/sr0
failed to read /dev/hda9
failed to read /dev/sde3
failed to read /dev/sda6
failed to read /dev/sdh9
failed to read /dev/hda8
failed to read /dev/sdg6
failed to read /dev/sdj3
failed to read /dev/fd1
failed to read /dev/hdd2
failed to read /dev/scd2
failed to read /dev/sdi9
failed to read /dev/sdk8
failed to read /dev/sdk6
failed to read /dev/sdh2
failed to read /dev/sdf3
failed to read /dev/scd7
failed to read /dev/sdi
failed to read /dev/cloop1
failed to read /dev/sdl7
failed to read /dev/hdd9
failed to read /dev/sdk5
failed to read /dev/sde2
failed to read /dev/sdj9
failed to read /dev/sdd9
failed to read /dev/hdb5
failed to read /dev/hdc8
failed to read /dev/sdi2
failed to read /dev/sdk1
failed to read /dev/sdh4
failed to read /dev/sdf2
failed to read /dev/sdc5
failed to read /dev/sdc8
failed to read /dev/fd0
failed to read /dev/hdc5
failed to read /dev/sde1
failed to read /dev/hdc1
failed to read /dev/sdc9
failed to read /dev/hda1
failed to read /dev/sdi6
failed to read /dev/sdh
failed to read /dev/sdd7
failed to read /dev/hdb9
failed to read /dev/sdg8
failed to read /dev/sdh3
failed to read /dev/sr6
failed to read /dev/sdb9
failed to read /dev/hdb8
failed to read /dev/hdd5
failed to read /dev/hda2
failed to read /dev/sdf8
failed to read /dev/sr8
failed to read /dev/sdh6
failed to read /dev/sdj4
failed to read /dev/sdl
failed to read /dev/sdf4
failed to read /dev/sde9
failed to read /dev/hdb2
failed to read /dev/sdl4
failed to read /dev/hda3
failed to read /dev/sde5
failed to read /dev/sda9
failed to read /dev/sdi7
failed to read /dev/sdj7
failed to read /dev/sde6
failed to read /dev/sde7
failed to read /dev/hdd
failed to read /dev/sdf9
failed to read /dev/sdk4
failed to read /dev/sdi3
failed to read /dev/sdd4
failed to read /dev/hda5
failed to read /dev/sdl9
failed to read /dev/hdc7
failed to read /dev/hdd6
failed to read /dev/sr5
failed to read /dev/sr7
failed to read /dev/sdb5
failed to read /dev/sdb4
failed to read /dev/sdh1
failed to read /dev/hdc2
failed to read /dev/hdd1
failed to read /dev/hdc3
failed to read /dev/sr3
failed to read /dev/scd6
failed to read /dev/hdc4
failed to read /dev/sdc3
failed to read /dev/sdl8
failed to read /dev/sr1
failed to read /dev/hdb1
failed to read /dev/sdl5
failed to read /dev/hdb7
failed to read /dev/hdc
failed to read /dev/sdj8
failed to read /dev/sr2
failed to read /dev/hdb3
failed to read /dev/sdd8
failed to read /dev/sdk9
failed to read /dev/sdi1
failed to read /dev/sdl1
failed to read /dev/sr4
failed to read /dev/sdj5
failed to read /dev/sr9
failed to read /dev/hdb
failed to read /dev/sda7
failed to read /dev/sdf6
failed to read /dev/sdf5
failed to read /dev/sdc7
failed to read /dev/sdi8
failed to read /dev/scd0
failed to read /dev/hdc6
failed to read /dev/sdk2
failed to read /dev/sdg4
failed to read /dev/hdd8
failed to read /dev/sdj2
failed to read /dev/sdk
failed to read /dev/sdd6
failed to read /dev/sda8
failed to read /dev/sdk7
failed to read /dev/scd3
failed to read /dev/scd4
failed to read /dev/hda7
failed to read /dev/sdk3
failed to read /dev/sdc6
failed to read /dev/sdj
failed to read /dev/sdj1
failed to read /dev/sdh5
failed to read /dev/sdd3
failed to read /dev/sdb6
failed to read /dev/sdg5
failed to read /dev/sdg7
failed to read /dev/sdb3
failed to read /dev/sdi5
failed to read /dev/sdc4
failed to read /dev/sdi4
failed to read /dev/sdd5
failed to read /dev/sdh7
failed to read /dev/sdb7
failed to read /dev/sde8
failed to read /dev/cloop
failed to read /dev/sdf7
failed to read /dev/sdl3
failed to read /dev/hda4
failed to read /dev/hdd4
failed to read /dev/sdh8
failed to read /dev/sdl2
failed to read /dev/sdb8
failed to read /dev/hdb6
failed to read /dev/scd8
failed to read /dev/sde4
Label: ''MMedia'' uuid: 120b036a-883f-46aa-bd9a-cb6a1897c8d2
Total devices 3 FS bytes used 3.72TB
devid 1 size 1.82TB used 1.27TB path /dev/sdg1
devid 2 size 1.81TB used 1.26TB path /dev/sdb1
devid 3 size 1.81TB used 1.27TB path /dev/sdc1
Btrfs Btrfs v0.19
--------------------------------------------------
# cat /proc/partitions
major minor #blocks name
8 0 293036184 sda
8 1 10490413 sda1
8 2 2104515 sda2
8 3 10490445 sda3
8 4 269948227 sda4
8 16 1953514584 sdb
8 17 1948684468 sdb1
8 18 4827532 sdb2
8 32 1953514584 sdc
8 33 1947881218 sdc1
8 34 5630782 sdc2
8 48 1465138584 sdd
8 49 1460308468 sdd1
8 50 4827532 sdd2
8 96 1953514584 sdg
8 97 1949487718 sdg1
8 98 4024282 sdg2
8 80 15613920 sdf
8 81 15609888 sdf1
------------------------------------------------------
Can I hope that this nasty behaviour gets fixed some day? I won''t use
"udev" just to fix it.
Viele Gruesse!
Helmut
--
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
On Fri, Oct 14, 2011 at 03:51:00PM +0200, Helmut Hullen wrote:> Hallo, linux-btrfs, > > I''ve just compiled kernel 3.9.04 and runDo you mean 3.0.4? We''ve not reached 3.2 yet, let alone 3.9 :) (Not that it matters in this case).> btrfs filesystem show > > On my system (Slackware 13.37, self made, without "udev") it still shows > a lot of non existent devices (I have shortened the list ...):This is not a kernel issue, it''s a purely userspace issue. Try the latest integration branch from git.darksatanic.net, which should have a fix for it. Hugo. -- === Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk == PGP key: 515C238D from wwwkeys.eu.pgp.net or http://www.carfax.org.uk --- emacs: Eighty Megabytes And Constantly Swapping. ---
Hallo, Hugo, Du meintest am 14.10.11:>> I''ve just compiled kernel 3.9.04 and run> Do you mean 3.0.4? We''ve not reached 3.2 yet, let alone 3.9 :) > (Not that it matters in this case).Sorry - bending the fingers is a hard work ... (and looking for typos too ...)> This is not a kernel issue, it''s a purely userspace issue. Try the > latest integration branch from git.darksatanic.net, which should have > a fix for it.Ok - have I to cross my fingers? Viele Gruesse! Helmut -- 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
Hallo, Hugo, Du meintest am 14.10.11:> This is not a kernel issue, it''s a purely userspace issue. Try the > latest integration branch from git.darksatanic.net, which should have > a fix for it.I''ve just tried git clone git://git.darksatanic.net/repo/btrfs-progs-unstable.git and got the answer + git clone git://git.darksatanic.net/repo/btrfs-progs-unstable.git git.darksatanic.net[0: 212.13.194.111]: errno=Connection refused git.darksatanic.net[0: 2001:ba8:1f1:f1d9:216:3eff:fe14:aef9]: errno=Network is unreachable fatal: unable to connect a socket (Network is unreachable) ----------------------------- Have I got just another typo (or user mistake), or is there another problem? Viele Gruesse! Helmut -- 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
On Fri, Oct 14, 2011 at 04:59:00PM +0200, Helmut Hullen wrote:> Hallo, Hugo, > Du meintest am 14.10.11: > > > This is not a kernel issue, it''s a purely userspace issue. Try the > > latest integration branch from git.darksatanic.net, which should have > > a fix for it. > > I''ve just tried > > git clone git://git.darksatanic.net/repo/btrfs-progs-unstable.git > > and got the answer > > + git clone git://git.darksatanic.net/repo/btrfs-progs-unstable.git > git.darksatanic.net[0: 212.13.194.111]: errno=Connection refused > git.darksatanic.net[0: 2001:ba8:1f1:f1d9:216:3eff:fe14:aef9]: errno=Network is unreachable > fatal: unable to connect a socket (Network is unreachable) > > ----------------------------- > > Have I got just another typo (or user mistake), or is there another > problem?It seems to be OK for me from here (the server is in a totally different network to where I am), so I think it must be a problem local to you. The IP addresses (both v4 and v6) look like the right ones, and I''m not aware of having any blocking in place from my service provider. Do you have a "transparent" proxy in the way? Hugo. -- === Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk == PGP key: 515C238D from wwwkeys.eu.pgp.net or http://www.carfax.org.uk --- UNIX: Japanese brand of food containers. ---
On Fri, Oct 14, 2011 at 05:14:32PM +0200, Tomasz Torcz wrote:> On Fri, Oct 14, 2011 at 04:08:24PM +0100, Hugo Mills wrote: > > On Fri, Oct 14, 2011 at 04:59:00PM +0200, Helmut Hullen wrote: > > > Du meintest am 14.10.11: > > > I''ve just tried > > > > > > git clone git://git.darksatanic.net/repo/btrfs-progs-unstable.git > > > > > > and got the answer > > > > > > + git clone git://git.darksatanic.net/repo/btrfs-progs-unstable.git > > > git.darksatanic.net[0: 212.13.194.111]: errno=Connection refused > > > git.darksatanic.net[0: 2001:ba8:1f1:f1d9:216:3eff:fe14:aef9]: errno=Network is unreachable > > > fatal: unable to connect a socket (Network is unreachable) > > > > > > ----------------------------- > > > > > > Have I got just another typo (or user mistake), or is there another > > > problem? > > I see the same problem from totally different network, tcptraceroute > to git port ends with:^^^^^^^^ D''oh. Sorry, I only just noticed this. I don''t run a git server -- you need http:// not git:// Hugo. -- === Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk == PGP key: 515C238D from wwwkeys.eu.pgp.net or http://www.carfax.org.uk --- UNIX: Japanese brand of food containers. ---
Hallo, Hugo, Du meintest am 14.10.11:>> I''ve just tried >> >> git clone git://git.darksatanic.net/repo/btrfs-progs-unstable.git >> >> and got the answer >> >> + git clone git://git.darksatanic.net/repo/btrfs-progs-unstable.git >> git.darksatanic.net[0: 212.13.194.111]: errno=Connection refused >> git.darksatanic.net[0: 2001:ba8:1f1:f1d9:216:3eff:fe14:aef9]: >> errno=Network is unreachable fatal: unable to connect a socket >> (Network is unreachable) >> >> ----------------------------- >> >> Have I got just another typo (or user mistake), or is there another >> problem?> It seems to be OK for me from here (the server is in a totally > different network to where I am), so I think it must be a problem > local to you. The IP addresses (both v4 and v6) look like the right > ones, and I''m not aware of having any blocking in place from my > service provider. Do you have a "transparent" proxy in the way?Changing from "git://" to "http://" solved the problem! Compiling worked, see <http://arktur.shuttle.de/CD/Testpakete/btrfs-progs-20111014-i486-1Mills_hln.txz> But "btrfs filesystem show" still shows lots of nonexistent devices - sorry. Viele Gruesse! Helmut -- 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
On Friday, 14 October, 2011 17:43:00 you wrote: [...]> > But "btrfs filesystem show" still shows lots of nonexistent devices - > sorry.You have to checkout the latest branch; so after $ git clone http://git.darksatanic.net/repo/btrfs-progs-unstable.git you have to perform $ cd btrfs-progs-unstable $ git checkout integration-20111012 Hoping that that help BR G.Baroncelli> > Viele Gruesse! > Helmut > -- > 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-- gpg key@ keyserver.linux.it: Goffredo Baroncelli (ghigo) <kreijack@inwind.it> Key fingerprint = 4769 7E51 5293 D36C 814E C054 BF04 F161 3DC5 0512 -- 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
Hallo, Goffredo, Du meintest am 14.10.11:> You have to checkout the latest branch; so after> $ git clone http://git.darksatanic.net/repo/btrfs-progs-unstable.git> you have to perform> $ cd btrfs-progs-unstable > $ git checkout integration-20111012> Hoping that that helpBingo! Now "btrfs filesystem show" works as desired - many thanks to Hugo! Viele Gruesse! Helmut -- 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
Hallo, Hugo, Du meintest am 14.10.11:>> btrfs filesystem show >> >> On my system (Slackware 13.37, self made, without "udev") it still >> shows a lot of non existent devices (I have shortened the list ...):> This is not a kernel issue, it''s a purely userspace issue. Try the > latest integration branch from git.darksatanic.net, which should have > a fix for it.When I use btrfs filesystem show with the "integration branch" then the non existing devices in "/dev/*" are not shown - fine. It shows (p.e.) devid ... /dev/sdb1 devid ... /dev/sdc1 devid ... /dev/sdd1 But when I use btrfsk /dev/sdb1 then btrfsck still shows all nonexisting devices. Viele Gruesse! Helmut -- 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