On Saturday 16 January 2010, you (Dipl.-Ing. Michael Niederle) wrote:
> Hi, Goffredo!
> 
> > Try btrfs-show
> 
> Thanks for your advice!
> 
> btrfs-show works but it displays a lot of error message for non-btrfs 
devices:
> 
> > btrfs-show
> failed to read /dev/sdg
> failed to read /dev/sdg1
> failed to read /dev/sdg2
> failed to read /dev/sdg3
> failed to read /dev/sdg4
> failed to read /dev/md1
> failed to read /dev/fd0
> failed to read /dev/fd0u1440
> failed to read /dev/fd1
> failed to read /dev/hda
> failed to read /dev/hda1
> failed to read /dev/hda10
> failed to read /dev/hda11
> failed to read /dev/hda12
> ...
> failed to read /dev/sr0
> failed to read /dev/sr1
> failed to read /dev/sr2
> failed to read /dev/sr3
> ...
> Label: Alpha4  uuid: 63b82dad-ed81-41f4-910f-7b358ceb77ba
>       Total devices 1 FS bytes used 11.81GB
>       devid    1 size 20.01GB used 20.01GB path /dev/sda3
> 
> Btrfs v0.19-4-gab8fb4c
> 
> Even if I try
> 
> btrfs-show /dev/sda3
> 
> I get the same output.
> 
> Greetings, Michael
> 
Yes they search in every block devices a btrfs file-system. It may be 
smarter/faster skipping the floppy and the cd-rom..

BR
G.Baroncelli

-- 
gpg key@ keyserver.linux.it: Goffredo Baroncelli (ghigo) <kreijackATinwind.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 majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to