Date: Wed, 21 May 2008 05:19:38 +0900 From: Daichi GOTO <daichi@freebsd.org> To: matteo@FreeBSD.org Cc: freebsd-bugs@FreeBSD.org, Masanori OZAWA <ozawa@ongs.co.jp> Subject: Re: bin/123574: [unionfs] df(1) -t option destroys info for unionfs (and maybe other) mounts Message-ID: <4833325A.2040103@freebsd.org> In-Reply-To: <200805170903.m4H93G09079190@freefall.freebsd.org> References: <200805170903.m4H93G09079190@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
matteo@FreeBSD.org wrote: > Synopsis: [unionfs] df(1) -t option destroys info for unionfs (and maybe other) mounts (snip) > User is running 6.3 which, IIRC, does not include the new unionfs implementation, but this > bug may be present in the new one too. Daichi surely knows whether this is the case. > > http://www.freebsd.org/cgi/query-pr.cgi?pr=123574 I suppose that this issue depends on implementation of df(1) not unionfs. Most case df gets filesystem information by getmntinfo(3), but in "df -t" case, it gets that by statfs(2). "df -t" uses statfs(2) with a target mount point, so "df -t" prints top layer filesystem information mount-count repeated. I guess that to fix this issue, the change of df(1) implementations is better way :) Do you know who is better man to maintain df(1) implementation? It seems that df(1) does not have active maintainer. -- Daichi GOTO, http://people.freebsd.org/~daichi
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4833325A.2040103>