From: Theodore Tso <tytso@MIT.EDU>
To: Eric Sandeen <sandeen@redhat.com>
Cc: ext4 development <linux-ext4@vger.kernel.org>
Subject: Re: blkid oddities with stale devices in the cache
Date: Sun, 6 Jul 2008 14:40:56 -0400 [thread overview]
Message-ID: <20080706184056.GB26084@mit.edu> (raw)
In-Reply-To: <48704BB9.1090501@redhat.com>
On Sat, Jul 05, 2008 at 11:36:09PM -0500, Eric Sandeen wrote:
> Eric Sandeen wrote:
> > This is w.r.t. https://bugzilla.redhat.com/show_bug.cgi?id=452333
> >
> > Dave had a few stale entries in blkid.tab; label from a usb key showed
> > up under several non-existent, stale device names. fstab had LABEL=,
> > mounting by label failed because blkid returned a stale, nonexistent device.
>
> Ted, ping (when you're done kernel-wrangling anyway)? Any thoughts on
> this? Returning cached data for a device when stat says ENOENT seems
> very weird (and wrong).
Check out what I just pushed out to the git repository. I think this
should solve the problems people have been reporting....
- Ted
prev parent reply other threads:[~2008-07-06 18:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-21 4:59 blkid oddities with stale devices in the cache Eric Sandeen
2008-07-06 4:36 ` Eric Sandeen
2008-07-06 18:40 ` Theodore Tso [this message]
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=20080706184056.GB26084@mit.edu \
--to=tytso@mit.edu \
--cc=linux-ext4@vger.kernel.org \
--cc=sandeen@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox