On Wed, Apr 30, 2014 at 02:31:18PM +0100, Frank Kingswood wrote:
> >>>> Device size: 10.00GiB
> >>>> FS occuppied: 5.00GiB
> >>>
> >>I found a bit unclear the "FS occupied" terms.
> >
> >We're running out of terms to describe and distinguish the space that
> >the filesystem uses.
>
> >'occupied' seemed like a good choice to me, though it may be not obvious
>
> The space that the filesystem uses in total seems to me is called the
> "size". It has nothing to do with utilization.
>
> /dev/sda6, ID: 2
> Device size: 10.00GiB
> Filesystem size: 5.00GiB
>
> and perhaps only show that "Device size" line if it differs from the
> filesystem size by more than a block.
I have noticed that the help text of 'btrfs fi resize' already uses
'occupy':
$ btrfs fi resize --help
usage: btrfs filesystem resize [devid:][+/-]<newsize>[gkm]|[devid:]max <path>
Resize a filesystem
If 'max' is passed, the filesystem will occupy all available space
on the device 'devid'.
First appeared in
commit 35401ac1902544637ac26634e139f04ae31c2cbf
Author: Goffredo Baroncelli <kreijack@xxxxxxxxx>
Date: Thu Mar 11 22:32:50 2010 +0100
I've been thinking about all the proposals and I'm not feeling
comfortable to pick the winner yet.
So, I'll hide the entry from the output for now so the patchset can be
pushed next step upstream but does not introduce something that's
visible in UI but not agreed on.
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
