Boston Linux & Unix (BLU) Home | Calendar | Mail Lists | List Archives | Desktop SIG | Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings
Linux Cafe | Meeting Notes | Blog | Linux Links | Bling | About BLU

BLU Discuss list archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: ext3 fsck on reboot

    Date: Sat, 03 May 2008 12:51:42 -0400 
   From: Tom Metro <[hidden email]> 

   Robert Krawitz wrote: 
   > On a 500 GB partition, even if extN only checks once every 30 reboots 
   > or so, it's going to take an awfully long time on those unusual 
   > occasions. 

   I use XFS on my big disks, so I haven't noticed this, but does 
   anyone know why this check isn't performed by a daemon running in 
   the background? Sure, it'd have to be read-only, but if it observed 
   problems, it could record where, and notify the user that they need 
   to reboot for repairs. The repairs should then happen pretty quick, 
   now that the locations have already been found. 

You wouldn't want to write to the filesystem if it's inconsistent (how 
do you know what's safe to write to and correct to read from?).  It's 
also a lot harder to validate the consistency of something that's 
changing behind your back. 

Robert Krawitz                                     <[hidden email]> 

Tall Clubs International  -- or 1-888-IM-TALL-2 
Member of the League for Programming Freedom -- mail [hidden email] 
Project lead for Gutenprint   --

"Linux doesn't dictate how I work, I dictate how Linux works." 
--Eric Crampton 

This message has been scanned for viruses and 
dangerous content by MailScanner, and is 
believed to be clean. 

Discuss mailing list 
[hidden email]

BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!

Boston Linux & Unix /