Date: Tue, 1 Oct 2013 11:50:18 -0700 From: aurfalien <aurfalien@gmail.com> To: Berend de Boer <berend@pobox.com> Cc: freebsd-fs@FreeBSD.org Subject: Re: zfs: the exponential file system from hell Message-ID: <A35A5587-E910-483E-AB02-C9079891CB0B@gmail.com> In-Reply-To: <87d2nohm91.wl%berend@pobox.com> References: <52457A32.2090105@fsn.hu> <77F6465C-4E76-4EE9-88B5-238FFB4E0161@sarenet.es> <20130930234401.GA68360@neutralgood.org> <BFAE1DDE-B8F8-40E5-9D9B-CF954D5D6457@mail.turbofuzz.com> <87d2nohm91.wl%berend@pobox.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Oct 1, 2013, at 11:36 AM, Berend de Boer wrote: >>>>>> "Jordan" =3D=3D Jordan Hubbard <jkh@mail.turbofuzz.com> writes: >=20 > Jordan> Given that we have the sources to df, I guess we should > Jordan> consider the question begged: Do we want to change it to > Jordan> DTRT for zfs filesystems? There's no Unix Law=99 that says > Jordan> "df(1) must use the output of statfs(2) directly and can > Jordan> use no longer sources of information!" >=20 > What an amount of emails to this list it would safe! >=20 > --=20 > In favour obviously, >=20 > Berend de Boer Well, a ZFS aware df would be cool but how would NFS clients on a diff = OS handle this? I'd say leave it alone and leave it to the sys admins to write a wrapper = for clients that tosses ssh to the server and runs the appropriate zfs = tool for expected space stats. - aurf=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?A35A5587-E910-483E-AB02-C9079891CB0B>