Subject: Re: PR 36963
To: der Mouse <mouse@Rodents.Montreal.QC.CA>
From: Bill Stouder-Studenmund <>
List: tech-kern
Date: 09/19/2007 10:46:47
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Wed, Sep 19, 2007 at 12:08:45PM -0400, der Mouse wrote:
> > /home is a mount point.  [...]  But it should be noted that the
> > postfix, postgresql, and apache users don't touch /home.  postgresql
> > resides under /var (which is directly under /), and they exhibit the
> > same kind of error.
> The closest common ancestor is, then, /, right?
> UTSLing makes me think that fstatvfs1() - the syscall that fails in
> your ktraces - does stuff walking up/down the directory tree, unless
> certain flags are given.  I'm beginning to suspect that something is
> weird with / when the system is hosed.  It sure looks to me as though
> the errors occur for, and only for, things that read / (as opposed to
> searching it), as if it loses its world read bit or some such.

The thing is that as I understand it, that should only happen if there's a
chroot going on. It's so that we hide a chroot's path (as seen in mount
point info) from the occupants.

> The real baffler to me is how logging out fixes it.  Do you have a
> program that just does a stat() and prints out the results?  Siccing
> that on / might reveal something interesting.


Take care,


Content-Type: application/pgp-signature
Content-Disposition: inline

Version: GnuPG v1.4.7 (NetBSD)