public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Dike <jdike@addtoit.com>
To: Matheus Izvekov <mizvekov@gmail.com>
Cc: Jan Engelhardt <jengelh@linux01.gwdg.de>,
	Neil Brown <neilb@suse.de>,
	linux-kernel@vger.kernel.org
Subject: Re: Who uses the 'nodev' flag in /proc/filesystems ???
Date: Mon, 20 Mar 2006 12:56:33 -0500	[thread overview]
Message-ID: <20060320175633.GA5797@ccure.user-mode-linux.org> (raw)
In-Reply-To: <305c16960603200817u3c8e4023nf2621245fdb0ed65@mail.gmail.com>

On Mon, Mar 20, 2006 at 01:17:59PM -0300, Matheus Izvekov wrote:
> If a filesystem is nodev, then what would you fsck? Am i missing something?

There's a UML filesystem for which the nodev-implies-no-fsck behavior
is inconvenient.  It stores its files as files on the host, where the
file metadata is stored separately from the file data.  If the two
fall out of sync after a crash, we need to fsck it.  In this case,
fsck would do a hostfs mount of the data and metadata (where the files
are available as they exist on the host) and fix things up.

So, in this case, the thing being fscked is a directory hierarchy on
the host.

				Jeff

  reply	other threads:[~2006-03-20 17:55 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-19  5:27 Who uses the 'nodev' flag in /proc/filesystems ??? Neil Brown
2006-03-19  9:27 ` Jan Engelhardt
2006-03-20  4:46   ` Neil Brown
2006-03-20 16:06     ` Jan Engelhardt
2006-03-20 16:17       ` Matheus Izvekov
2006-03-20 17:56         ` Jeff Dike [this message]
2006-03-20 19:22           ` Matheus Izvekov
2006-03-20 19:48             ` Jeff Dike
2006-03-20 19:58               ` Jan Engelhardt
2006-03-21  0:32                 ` Jeff Dike
2006-03-21 17:31                   ` Jan Engelhardt
2006-03-20 21:14 ` Andreas Schwab

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=20060320175633.GA5797@ccure.user-mode-linux.org \
    --to=jdike@addtoit.com \
    --cc=jengelh@linux01.gwdg.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mizvekov@gmail.com \
    --cc=neilb@suse.de \
    /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