All of lore.kernel.org
 help / color / mirror / Atom feed
From: Theodore Tso <tytso@mit.edu>
To: "Andrés G. Aragoneses [ knocte ]" <knocte@gmail.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: Discussion about a "dirty bit" in the filesystem
Date: Sat, 21 Oct 2006 21:09:50 -0400	[thread overview]
Message-ID: <20061022010950.GC9082@thunk.org> (raw)
In-Reply-To: <ehdt24$iau$1@sea.gmane.org>

On Sat, Oct 21, 2006 at 09:39:02PM +0200, "Andrés G. Aragoneses [ knocte ]" wrote:
> Hello. Sorry if this is not the correct place to talk about this.
> 
> I am writing to this list because I am a user of openSUSE that opened
> filed a bug [1] against the issue tracking software of this linux
> distribution about boot management and hibernation. There was a
> discussion and then the bug was resolved to WONTFIX, but I think we
> could extract from it a nice FEATURE that any filesystem would have, or,
> in particular, ext4.
> 
> [1] https://bugzilla.novell.com/show_bug.cgi?id=175939
> 
> Any opinions?

I'm not at all sure what this has to do with ext4 at all.  The last
message indicates a major problem with your request, which is that if
a FAT partition is mounted by Linux, and in the middle of being
modified when the system is undergoing hibernation, and then Windows
is booted and modifies the filesystem, you can lose data.  But that's
because the FAT filesystem can be understood by both Windows and
Linux.  (Presumably this problem would also occur, in a much worse
case, using NTFS.)  But this has nothing to do with ext4.

I can imagine someone writing an improved hibernate script which
checks to see if a filesystem which could be understood by Windows
(i.e., FAT or NTFS) is mounted, and if any such filesystems are
mounted, disable the ability to boot into Windows after the
hibernation.  I could even imagine an improved hibernate script which
detects this case, and attempts to unmount the FAT and NTFS
filesystems, and if it could successfully unmount them all, allow the
user to reboot into Windows after hibernation.

However, this is not a ext4 filesystem matter, and not a kernel
matter, but rather a hibernation script issue.

Regards,

						- Ted

  reply	other threads:[~2006-10-22  1:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-21 19:39 Discussion about a "dirty bit" in the filesystem "Andrés G. Aragoneses [ knocte ]"
2006-10-22  1:09 ` Theodore Tso [this message]
2006-11-01 19:24   ` "Andrés G. Aragoneses [ knocte ]"

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=20061022010950.GC9082@thunk.org \
    --to=tytso@mit.edu \
    --cc=knocte@gmail.com \
    --cc=linux-ext4@vger.kernel.org \
    /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.