From: Martin Steigerwald <Martin@lichtvoll.de>
To: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH V2][BTRFS-PROGS] Enhance btrfs fi df with raid5/6 support
Date: Tue, 26 Feb 2013 14:15:16 +0100 [thread overview]
Message-ID: <201302261415.17070.Martin@lichtvoll.de> (raw)
In-Reply-To: <201302261358.55623.Martin@lichtvoll.de>
Am Dienstag, 26. Februar 2013 schrieb Martin Steigerwald:
> Am Dienstag, 26. Februar 2013 schrieb Gareth Pye:
> > On Tue, Feb 26, 2013 at 10:09 PM, Martin Steigerwald
> >
> > <Martin@lichtvoll.de> wrote:
> > > I´d still like that for df, whose output is quite bogus in certain
> > > BTRFS setups at the moment and does not give applications a realistic
> > > estimate at all. One example is raid 1 with 10 GB each disk. Shows 20
> > > GB free. An application which wants to write 15 GB will fail. Which
> > > can break installer scripts, package management, cache software or
> > > anything else which checks for free space. Thus I´d like df to
> > > default to *minimum* free.
> >
> > Is that any better than the script failing to attempt to install
> > because it needs 15G but because some of the storage is used in RAID1
> > then df shows 10G free but the 15G install would work fine. If you
> > could force the tool to install where it know it doesn't have
> > sufficient space?
>
> I do not quite understand your question. In RAID-1 with 10 GB and two
> disks, df will show 20 GB free. If the script needs 15 GB and checks for
> it it would run, but then fail. I would prefer that the script space
> check bails out in that case it is know that there is not enough space
> available anymore.
Well, okay, and exactly that is not known, cause if the files the installer
script are installed are stored a single instead of RAID-1 there would be
enough space.
Anyway for the additions Goffredo made I strongly suggest reading the old
discussions before starting to discuss stuff that has already been discussed
back then.
--
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7
next prev parent reply other threads:[~2013-02-26 13:15 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-23 13:46 [PATCH V2][BTRFS-PROGS] Enhance btrfs fi df with raid5/6 support Goffredo Baroncelli
2013-02-23 13:46 ` [PATCH 1/8] Add some helpers to manage the strings allocation/deallocation Goffredo Baroncelli
2013-02-25 2:20 ` Eric Sandeen
2013-02-25 19:59 ` Goffredo Baroncelli
2013-02-25 20:19 ` Zach Brown
2013-02-25 21:00 ` Goffredo Baroncelli
2013-02-23 13:46 ` [PATCH 2/8] Enhance the command btrfs filesystem df Goffredo Baroncelli
2013-02-23 13:46 ` [PATCH 3/8] Create the man page entry for the command btrfs fi df Goffredo Baroncelli
2013-02-23 13:46 ` [PATCH 4/8] Add helpers functions to handle the printing of data in tabular format Goffredo Baroncelli
2013-02-23 13:46 ` [PATCH 5/8] Add command btrfs filesystem disk-usage Goffredo Baroncelli
2013-02-23 13:46 ` [PATCH 6/8] Create entry in man page for " Goffredo Baroncelli
2013-02-23 13:46 ` [PATCH 7/8] Add btrfs device disk-usage command Goffredo Baroncelli
2013-02-23 13:46 ` [PATCH 8/8] Create a new entry in btrfs man page for btrfs device disk-usage Goffredo Baroncelli
2013-02-25 17:38 ` [PATCH V2][BTRFS-PROGS] Enhance btrfs fi df with raid5/6 support Zach Brown
2013-02-26 11:09 ` Martin Steigerwald
2013-02-26 11:28 ` Gareth Pye
2013-02-26 12:58 ` Martin Steigerwald
2013-02-26 13:15 ` Martin Steigerwald [this message]
2013-02-26 12:55 ` Martin Steigerwald
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=201302261415.17070.Martin@lichtvoll.de \
--to=martin@lichtvoll.de \
--cc=linux-btrfs@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).