From: Goffredo Baroncelli <kreijack@gmail.com>
To: "Dipl.-Ing. Michael Niederle" <mniederle@gmx.at>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Free space left
Date: Sat, 16 Jan 2010 20:20:08 +0100 [thread overview]
Message-ID: <201001162020.08633.kreijack@libero.it> (raw)
In-Reply-To: <20100116201733.1e30dad1@simplux>
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
next prev parent reply other threads:[~2010-01-16 19:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-16 15:41 Free space left Michael Niederle
2010-01-16 19:10 ` Goffredo Baroncelli
2010-01-16 19:17 ` Dipl.-Ing. Michael Niederle
2010-01-16 19:20 ` Goffredo Baroncelli [this message]
2010-01-16 19:31 ` Svein Erik Brostigen
2010-01-16 19:34 ` Goffredo Baroncelli
2010-01-16 19:46 ` Mathieu Chouquet-Stringer
2010-01-16 20:01 ` Goffredo Baroncelli
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=201001162020.08633.kreijack@libero.it \
--to=kreijack@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=mniederle@gmx.at \
/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