From: Ian Kent <raven@themaw.net>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: autofs@linux.kernel.org
Subject: Re: Very strange autofs failure on 2.6.30-rc2 with autofs-5.0.3-41 (fc10)
Date: Sat, 18 Apr 2009 10:58:06 +0800 [thread overview]
Message-ID: <49E941BE.3080706@themaw.net> (raw)
In-Reply-To: <49E90A39.3040102@zytor.com>
H. Peter Anvin wrote:
> I have been using for a very long time a setup where /home is an autofs
> from a plain indirect NIS map, but my personal home directory
> (/home/hpa) is simply a bind mount from /export/home/hpa. A
> straightforward use of autofs.
>
> I just rebooted my system yesterday, however, and found that all the
> directory entries in my home directory had gotten replaced with ghost
> directories -- and even more confusingly, the date wasn't the current
> date, but was back in 2008.
>
> The ghost directories were "sterile" in the sense that entering them
> wouldn't show the proper contents of those directories. As a result,
> massive failure.
>
> After suspecting filesystem corruption, and this, that and the other
> thing, I found that this was only when viewing though autofs
> (/home/hpa), and that the real filesystem (/export/home/hpa) was fully
> intact. Somehow autofs had ended up ghosting pretty much my entire
> directory, and doing so in some incorrect fashion.
>
> Replacing /home with a plain bind mount (no autofs) to /export/home
> resolved the issue.
This failure sounds rather more spectacular than should result from a
known problem we have with a recent init scripts change. I'll investigate.
Have a look at https://bugzilla.redhat.com/show_bug.cgi?id=475002.
Ian
next prev parent reply other threads:[~2009-04-18 2:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-17 23:01 Very strange autofs failure on 2.6.30-rc2 with autofs-5.0.3-41 (fc10) H. Peter Anvin
2009-04-18 2:58 ` Ian Kent [this message]
2009-04-20 5:34 ` Ian Kent
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=49E941BE.3080706@themaw.net \
--to=raven@themaw.net \
--cc=autofs@linux.kernel.org \
--cc=hpa@zytor.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.