Hello,
because creating/using filesystems in ZFS becoms cheap it is useful now
to create/organize filesystems in hierarchy:
bash-3.00# zfs list
NAME USED AVAIL REFER MOUNTPOINT
dns-pool 136K 43.1G 25.5K /dns-pool
dns-pool/zones 50K 43.1G 25.5K
[EMAIL PROTECTED] wrote:
Hello,
because creating/using filesystems in ZFS becoms cheap it is useful now
to create/organize filesystems in hierarchy:
bash-3.00# zfs list
NAME USED AVAIL REFER MOUNTPOINT
dns-pool 136K 43.1G 25.5K /dns-pool
dns-pool/zones
[EMAIL PROTECTED] wrote:
On Mon, Jul 10, 2006 at 05:07:35PM +0800, Darren Reed wrote:
[EMAIL PROTECTED] wrote:
Hello,
because creating/using filesystems in ZFS becoms cheap it is useful now
to create/organize filesystems in hierarchy:
bash-3.00# zfs list
NAME USED
Jeff Victor wrote:
[EMAIL PROTECTED] wrote:
bash-3.00# zfs list
NAME USED AVAIL REFER MOUNTPOINT
dns-pool 136K 43.1G 25.5K /dns-pool
dns-pool/zones 50K 43.1G 25.5K /dns-pool/zones
dns-pool/zones/dns1 24.5K 43.1G 24.5K /dns-pool/zones/dns1
Darren J Moffat wrote:
Jeff Victor wrote:
[EMAIL PROTECTED] wrote:
bash-3.00# zfs list
NAME USED AVAIL REFER MOUNTPOINT
dns-pool 136K 43.1G 25.5K /dns-pool
dns-pool/zones 50K 43.1G 25.5K /dns-pool/zones
dns-pool/zones/dns1 24.5K 43.1G
Darren J Moffat wrote:
Jeff Victor wrote:
[EMAIL PROTECTED] wrote:
bash-3.00# zfs list
NAME USED AVAIL REFER MOUNTPOINT
dns-pool 136K 43.1G 25.5K /dns-pool
dns-pool/zones 50K 43.1G 25.5K /dns-pool/zones
dns-pool/zones/dns1 24.5K 43.1G
Jeff Victor wrote:
My interpretation: more specific control of column widths and
flexibility to place the name in the first column. Further, to many
people, tabs are evil.
Putting the name in the first column is easy it works already:
zfs list -o name,used,avail,refer,mountpoint
Granted
Darren Reed wrote:
The width of the columns. Create a ZFS filesystem called
cube/builds/example_with_a_long_name and put that in the middle of your
output.
Even with one tab, that doesn't quite work for tty output.
The whole point of the -H is so that you can post process it to suit,
for
This is a known problem:
6349494 'zfs list' output annoying for even moderately long dataset names
The fix is fairly straightforward. We don't need some complicated
method of specifying columns widths. We just need to do two passes over
the data (which we already have in hand for sorting
