On 04/30/2014 03:37 PM, David Taylor wrote: > On Wed, 30 Apr 2014, Frank Kingswood wrote: >> On 30/04/14 13:11, David Sterba wrote: >>> On Wed, Apr 30, 2014 at 01:39:27PM +0200, Goffredo Baroncelli wrote: >>>> >>>> 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 > > FS size was what I was about to suggest, before I saw your reply. Pay attention that this value is not the Filesystem size, but to the maximum space the of THE DEVICE the filesystem is allowed to use. The filesystem size (the space available or the sum of the space available and the one occupied) is based on this value but it should be very different (think about a RAID 1 on three device of different sizes....) > > It makes more sense to me than 'Occupied' and seems cleaner than > 'Resized To'. It sort of mirrors how LVM describes PV / VG / LV > sizes, too. > -- gpg @keyserver.linux.it: Goffredo Baroncelli (kreijackATinwind.it> Key fingerprint BBF5 1610 0B64 DAC6 5F7D 17B2 0EDA 9B37 8B82 E0B5 -- 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
