 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
Windows Forum / Windows Me / System Tools / May 2005What is FsInfoSector ?
I found zilch in the MSKB about this. Often scandisk will report this as a corrected error, usually on C: The drive contained an error in its FSInfoSector. Resolution: Repair the error Results: Error was corrected as specified above. I "assume" FS = file system, MBR related ? Thanks -- Keyboard not detected Press F1 to continue FSInfoSector is the location on a hard disk where the amount of free space of the drive is recorded. Because the amount of free space on a drive is continually changing the system doesn't continually update this value but instead stores the amount of free space on each drive in memory and only writes it back to disk when the system shuts down. If however the system stops abnormally the recorded amount of free space on the drive doesn't get written back and the value of the record is incorrect and this is what scandisk is checking and correcting.  SignatureMike Maltby MS-MVP mike.maltby@gmail.com > I found zilch in the MSKB about this. Often scandisk > will report this as a corrected error, usually on C: [quoted text clipped - 5 lines] > I "assume" FS = file system, MBR related ? > Thanks Just to try to add a little 're-assurance' to Mike's reply, that message is usually contained in 'scandisk.log' (if enabled) in the root folder which is generated after each 'forced' scandisk and refers only to the C: drive (System Drive). If Windows doesn't shut down properly - e.g. power fail, or switching your PC off before it has shut itself down correctly, etc. - the FSInfoSector becomes corrupted due to this forced shutdown. (As explained by Mike) When the power is re-connected, the computer will re-boot forcing scandisk to run, which in turn detects this corrupted "File System Information Sector" and repairs it. So long as that is all that happened - i.e. NOT a damaged disk - then it is quite normal and can be ignored. Scandisk is working correctly and doing its job. Mart > FSInfoSector is the location on a hard disk where the amount of free space > of the drive is recorded. Because the amount of free space on a drive is [quoted text clipped - 14 lines] >> I "assume" FS = file system, MBR related ? >> Thanks I concur with Mike M and Mart: Crazy Error Messages ScanDisk keeps telling me that an FSInfoSector error was detected and corrected. If it was corrected, how come it keeps coming back? And how can I correct it permanently? http://www.pcworld.com/howto/article/0,aid,108742,pg,2,00.asp http://members.tripod.com/~averstak/fatdox/bootsec.htm SignatureJack E. Martinelli 2002-05 MS MVP for Shell/User / DTS Help us help you: http://www.dts-L.org/goodpost.htm In Memorium: Alex Nichol http://www.microsoft.com/windowsxp/expertzone/meetexperts/nichol.mspx Your cooperation is very appreciated. ------ > Just to try to add a little 're-assurance' to Mike's reply, that message is > usually contained in 'scandisk.log' (if enabled) in the root folder which is [quoted text clipped - 33 lines] > >> I "assume" FS = file system, MBR related ? > >> Thanks Got it ! Thank you >Just to try to add a little 're-assurance' to Mike's reply, that message is >usually contained in 'scandisk.log' (if enabled) in the root folder which is [quoted text clipped - 33 lines] >>> I "assume" FS = file system, MBR related ? >>> Thanks -- Keyboard not detected Press F1 to continue On Wed, 25 May 2005 00:45:59 +0100, "Mike M" >FSInfoSector is the location on a hard disk where the amount of free space >of the drive is recorded. Because the amount of free space on a drive is >continually changing the system doesn't continually update this value but >instead stores the amount of free space on each drive in memory and only >writes it back to disk when the system shuts down. Just a bit more detail on this. Firstly, it wasn't always like this. Prior to FAT32, the free space was calculated directly from the file system's FAT, probably by counting up all the clusters set as 0 (available) within the FAT. That was OK when FAT12 and FAT16 meant small FATs with 12- or 16-bit values. The overhead became untenable when FAT32 allowed far larger FAT with the bulkier 32-bit addresses. This is when the free space value started to be cached within an extended partition (volume) boot record, which went from 1 sector to 3 sectors in size. Because this constantly-changing value is outside of the first sector of the boot record, anything that blocks writes to the traditional boot record or monitors this for changes, will still work. As Mike says, the cached value is kept up to date in a "lazy" way, i.e. not after every file system operation. I doubt if it is left "stale" from boot right through to shutdown, though; I'd expect it to get flushed to disk along with other pending file system writes. Bad exits may leave a mismatch between this cached value and the actual free space, and other repairs to the file system may further change the actual free space and thus invalidate the cached value. So it's common to see file system checkers report this value as invalid. As it is a derived value, based on the reality as set in the FAT, it is trivial and safe to "fix". >---------- ----- ---- --- -- - - - - Gone to bloggery: http://cquirke.blogspot.com >---------- ----- ---- --- -- - - - - Got it ! Thank you >FSInfoSector is the location on a hard disk where the amount of free space >of the drive is recorded. Because the amount of free space on a drive is [quoted text clipped - 4 lines] >get written back and the value of the record is incorrect and this is what >scandisk is checking and correcting. -- Keyboard not detected Press F1 to continue |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2008 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.