linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andries Brouwer <aebr@win.tue.nl>
To: Matthew Wilcox <willy@debian.org>
Cc: Bryan Henderson <hbryan@us.ibm.com>,
	anil vijarnia <linux_fs@rediffmail.com>,
	linux-fsdevel@vger.kernel.org
Subject: Re: clean unmount?
Date: Tue, 11 Mar 2003 00:48:00 +0100	[thread overview]
Message-ID: <20030310234800.GA4357@win.tue.nl> (raw)
In-Reply-To: <20030310232322.GB21234@parcelfarce.linux.theplanet.co.uk>

On Mon, Mar 10, 2003 at 11:23:22PM +0000, Matthew Wilcox wrote:

> > I don't know how the "clean unmount" information is represented in FAT.
> 
> OSR2 includes versions of the Io.sys and Win.com files that check the
> Clean Shutdown and Hard Disk Error bits in the Virtual File Allocation
> Table (VFAT) during startup. If either of these bits is turned on (that
> is, cleared to 0) on any drive present in real mode, you are prompted to
> run ScanDisk.
> 
> The Clean Shutdown and Hard Disk Error bits are the two low-order bits of
> the FAT entry for cluster 1. If bit 0 is 0, it indicates an unclean
> shutdown; if bit 1 is 0, it indicates that a hard disk error occurred on
> that drive. These bits are turned on by VFAT; they are turned off only by
> ScanDisk. The Clean Shutdown bit is turned off upon completion of a
> standard run. The Hard Disk Error bit is turned off upon completion of a
> surface scan (regardless of whether errors were repaired).

My docs say "high-order" instead of "low-order".
Are there people with a Windows system so that they can check?

Andries

http://www.win.tue.nl/~aeb/linux/fs/fat/fat-1.html#ss1.3.1


  reply	other threads:[~2003-03-10 23:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-07  5:26 clean unmount? anil  vijarnia
2003-03-10 23:12 ` Bryan Henderson
2003-03-10 23:23   ` Matthew Wilcox
2003-03-10 23:48     ` Andries Brouwer [this message]
2003-03-13  4:40       ` H. Peter Anvin
  -- strict thread matches above, loose matches on Subject: below --
2003-03-07  5:24 anil  vijarnia

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=20030310234800.GA4357@win.tue.nl \
    --to=aebr@win.tue.nl \
    --cc=hbryan@us.ibm.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux_fs@rediffmail.com \
    --cc=willy@debian.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).