Hello all,
do you know where can I find the dirty bit for a volume (the chkdsk /f sets the dirty bit on the volume).
I want to read it’s state
Any help appreciated
Best:
Mark
Hello all,
do you know where can I find the dirty bit for a volume (the chkdsk /f sets the dirty bit on the volume).
I want to read it’s state
Any help appreciated
Best:
Mark
For FAT16 and FAT32, the file system driver may use the high two bits of the
FAT[1] entry(EOC) for dirty volume flags.
For FAT16:
ClnShutBitMask : 0x8000;
HrdErrBitMask : 0x4000;
For FAT32:
ClnShutBitMask : 0x8000000;
HrdErrBitMask : 0x4000000;
Bit ClnShutBitMask - If bit is 1, volume is clean. If bit is 0 volume is
dirty.
Bit HrdErrBitMask - If bit is 1, no disk read/write errors were
encountered. If 0, the file system driver encountered an I/O error on volume
the last time it was mounted.
Hope this may help you.
Warm Regards
Anish
-----Original Message-----
From: Mark Twain [mailto:xxxxx@crosswinds.net]
Sent: Wednesday, June 28, 2000 5:00 PM
To: File Systems Developers
Subject: [ntfsd] Dirty volume
Hello all,
do you know where can I find the dirty bit for a volume (the chkdsk /f sets
the dirty bit on the volume).
I want to read it’s state
Any help appreciated
Best:
Mark
Thank you very much, Anish,
but I need the addresses for NTFS volumes…
If you can tell me something…
Best:
Mark
----- Original Message -----
From: ANISH NAIR
To: File Systems Developers
Sent: Wednesday, June 28, 2000 1:22 PM
Subject: [ntfsd] RE: Dirty volume
For FAT16 and FAT32, the file system driver may use the high two bits of the FAT[1] entry(EOC) for dirty volume flags.
For FAT16:
ClnShutBitMask : 0x8000;
HrdErrBitMask : 0x4000;
For FAT32:
ClnShutBitMask : 0x8000000;
HrdErrBitMask : 0x4000000;
Bit ClnShutBitMask - If bit is 1, volume is clean. If bit is 0 volume is dirty.
Bit HrdErrBitMask - If bit is 1, no disk read/write errors were encountered. If 0, the file system driver encountered an I/O error on volume the last time it was mounted.
Hope this may help you.
Warm Regards
Anish
-----Original Message-----
From: Mark Twain [mailto:xxxxx@crosswinds.net]
Sent: Wednesday, June 28, 2000 5:00 PM
To: File Systems Developers
Subject: [ntfsd] Dirty volume
Hello all,
do you know where can I find the dirty bit for a volume (the chkdsk /f sets the dirty bit on the volume).
I want to read it’s state
Any help appreciated
Best:
Mark
I think some more generic path will be when using the
IRP_MJ_FILE_SYSTEM_CONTROL:
FSCTL_IS_VOLUME_DIRTY
FSCTL_MARK_VOLUME_DIRTY
If you want to get this flag right from the disk you have to know
there is no correct path to do this generically (except of FsControl).
Best regards
Paul
-----P?vodn? zpr?va-----
Od: Mark Twain [SMTP:xxxxx@crosswinds.net]
Odesl?no: 28. ?ervna 2000 15:34
Komu: File Systems Developers
P?edm?t: [ntfsd] RE: Dirty volumeThank you very much, Anish,
but I need the addresses for NTFS volumes…
If you can tell me something…Best:
Mark----- Original Message -----
From: ANISH NAIR mailto:xxxxx
> To: File Systems Developers mailto:xxxxx
> Sent: Wednesday, June 28, 2000 1:22 PM
> Subject: [ntfsd] RE: Dirty volume
>
> For FAT16 and FAT32, the file system driver may use the high two
> bits of the FAT[1] entry(EOC) for dirty volume flags.
> For FAT16:
> ClnShutBitMask : 0x8000;
> HrdErrBitMask : 0x4000;
>
> For FAT32:
>
> ClnShutBitMask : 0x8000000;
> HrdErrBitMask : 0x4000000;
>
> Bit ClnShutBitMask - If bit is 1, volume is clean. If bit is 0
> volume is dirty.
> Bit HrdErrBitMask - If bit is 1, no disk read/write errors were
> encountered. If 0, the file system driver encountered an I/O error on
> volume the last time it was mounted.
>
> Hope this may help you.
>
>
>
>
>
> Warm Regards
> Anish
>
>
>
> -----Original Message-----
> From: Mark Twain [mailto:xxxxx@crosswinds.net]
> Sent: Wednesday, June 28, 2000 5:00 PM
> To: File Systems Developers
> Subject: [ntfsd] Dirty volume
>
>
> Hello all,
> do you know where can I find the dirty bit for a volume (the
> chkdsk /f sets the dirty bit on the volume).
> I want to read it’s state
> Any help appreciated
>
> Best:
> Mark
></mailto:xxxxx></mailto:xxxxx>
And how can prevent the dirty flag from the NTFS volume?
I mean, how can I set it back to “normal” state?
Best:
Mark
----- Original Message -----
From: Pavel Hrdina
To: File Systems Developers
Sent: Wednesday, June 28, 2000 3:19 PM
Subject: [ntfsd] RE: Dirty volume
> I think some more generic path will be when using the
> IRP_MJ_FILE_SYSTEM_CONTROL:
> FSCTL_IS_VOLUME_DIRTY
> FSCTL_MARK_VOLUME_DIRTY
>
> If you want to get this flag right from the disk you have to know
> there is no correct path to do this generically (except of FsControl).
>
> Best regards
>
> Paul
>
> > -----P?vodn? zpr?va-----
> > Od: Mark Twain [SMTP:xxxxx@crosswinds.net]
> > Odesl?no: 28. ?ervna 2000 15:34
> > Komu: File Systems Developers
> > P?edm?t: [ntfsd] RE: Dirty volume
> >
> > Thank you very much, Anish,
> > but I need the addresses for NTFS volumes…
> > If you can tell me something…
> >
> > Best:
> > Mark
> >
> > ----- Original Message -----
> > From: ANISH NAIR mailto:xxxxx
> > To: File Systems Developers mailto:xxxxx
> > Sent: Wednesday, June 28, 2000 1:22 PM
> > Subject: [ntfsd] RE: Dirty volume
> >
> > For FAT16 and FAT32, the file system driver may use the high two
> > bits of the FAT[1] entry(EOC) for dirty volume flags.
> > For FAT16:
> > ClnShutBitMask : 0x8000;
> > HrdErrBitMask : 0x4000;
> >
> > For FAT32:
> >
> > ClnShutBitMask : 0x8000000;
> > HrdErrBitMask : 0x4000000;
> >
> > Bit ClnShutBitMask - If bit is 1, volume is clean. If bit is 0
> > volume is dirty.
> > Bit HrdErrBitMask - If bit is 1, no disk read/write errors were
> > encountered. If 0, the file system driver encountered an I/O error on
> > volume the last time it was mounted.
> >
> > Hope this may help you.
> >
> >
> >
> >
> >
> > Warm Regards
> > Anish
> >
> >
> >
> > -----Original Message-----
> > From: Mark Twain [mailto:xxxxx@crosswinds.net]
> > Sent: Wednesday, June 28, 2000 5:00 PM
> > To: File Systems Developers
> > Subject: [ntfsd] Dirty volume
> >
> >
> > Hello all,
> > do you know where can I find the dirty bit for a volume (the
> > chkdsk /f sets the dirty bit on the volume).
> > I want to read it’s state
> > Any help appreciated
> >
> > Best:
> > Mark
> >
>
> —
> You are currently subscribed to ntfsd as: xxxxx@crosswinds.net
> To unsubscribe send a blank email to $subst(‘Email.Unsub’)
></mailto:xxxxx></mailto:xxxxx>
Only checkdisk is allowed to clear this flag, I think.
You can only set it, no clear it.
Paul
-----P?vodn? zpr?va-----
Od: Mark Twain [SMTP:xxxxx@crosswinds.net]
Odesl?no: 28. ?ervna 2000 17:01
Komu: File Systems Developers
P?edm?t: [ntfsd] RE: Dirty volumeAnd how can prevent the dirty flag from the NTFS volume?
I mean, how can I set it back to “normal” state?Best:
Mark
----- Original Message -----
From: Pavel Hrdina
> To: File Systems Developers
> Sent: Wednesday, June 28, 2000 3:19 PM
> Subject: [ntfsd] RE: Dirty volume
>
>
> > I think some more generic path will be when using the
> > IRP_MJ_FILE_SYSTEM_CONTROL:
> > FSCTL_IS_VOLUME_DIRTY
> > FSCTL_MARK_VOLUME_DIRTY
> >
> > If you want to get this flag right from the disk you have to know
> > there is no correct path to do this generically (except of FsControl).
> >
> > Best regards
> >
> > Paul
> >
> > > -----P?vodn? zpr?va-----
> > > Od: Mark Twain [SMTP:xxxxx@crosswinds.net]
> > > Odesl?no: 28. ?ervna 2000 15:34
> > > Komu: File Systems Developers
> > > P?edm?t: [ntfsd] RE: Dirty volume
> > >
> > > Thank you very much, Anish,
> > > but I need the addresses for NTFS volumes…
> > > If you can tell me something…
> > >
> > > Best:
> > > Mark
> > >
> > > ----- Original Message -----
> > > From: ANISH NAIR mailto:xxxxx
> > > To: File Systems Developers mailto:xxxxx
> > > Sent: Wednesday, June 28, 2000 1:22 PM
> > > Subject: [ntfsd] RE: Dirty volume
> > >
> > > For FAT16 and FAT32, the file system driver may use the high two
> > > bits of the FAT[1] entry(EOC) for dirty volume flags.
> > > For FAT16:
> > > ClnShutBitMask : 0x8000;
> > > HrdErrBitMask : 0x4000;
> > >
> > > For FAT32:
> > >
> > > ClnShutBitMask : 0x8000000;
> > > HrdErrBitMask : 0x4000000;
> > >
> > > Bit ClnShutBitMask - If bit is 1, volume is clean. If bit is 0
> > > volume is dirty.
> > > Bit HrdErrBitMask - If bit is 1, no disk read/write errors were
> > > encountered. If 0, the file system driver encountered an I/O error on
> > > volume the last time it was mounted.
> > >
> > > Hope this may help you.
> > >
> > >
> > >
> > >
> > >
> > > Warm Regards
> > > Anish
> > >
> > >
> > >
> > > -----Original Message-----
> > > From: Mark Twain [mailto:xxxxx@crosswinds.net]
> > > Sent: Wednesday, June 28, 2000 5:00 PM
> > > To: File Systems Developers
> > > Subject: [ntfsd] Dirty volume
> > >
> > >
> > > Hello all,
> > > do you know where can I find the dirty bit for a volume (the
> > > chkdsk /f sets the dirty bit on the volume).
> > > I want to read it’s state
> > > Any help appreciated
> > >
> > > Best:
> > > Mark
> > >
> >
> > —
> > You are currently subscribed to ntfsd as: xxxxx@crosswinds.net
> > To unsubscribe send a blank email to $subst(‘Email.Unsub’)
> >
>
>
> —
> You are currently subscribed to ntfsd as: xxxxx@sodatsw.cz
> To unsubscribe send a blank email to $subst(‘Email.Unsub’)</mailto:xxxxx></mailto:xxxxx>