I'm running an OpenAFS/Debian server on a 1 TB SATA drive, connected via a 1520 
Rocketraid PCI card  (This is a "lab" and not a critical production 
environment, if that wasn't immediately apparent).
 
I had all my partitions set up as Ext3, but I started having trouble with FSCK 
checks at boot.  FSCK would just hang on /vicepa, even when I tried running it 
manually, so I disabled the boot check on that (my AFS) partition.  When I 
ran my hard drive manufacturer's disk utility I found errors on the drive which 
were subsequently corrected.  Then I read more about Ext3s journaling, speed, 
etc., and I decided to switch /vicepa to Ext2 (the other partitions remain 
Ext3) just to see whether it made any difference.  It seems that FSCK now runs 
without a problem.
 
So I'm wondering whether you have any advice or comments about any of this.  
Whether, for instance, it's bad to mix filesystem types in this context?  
Whether FSCK has issues with journaled filesystems?  It seems that if I stay 
with Ext2, what I'm losing specifically is  better chance of recovery in the 
event of a power loss or other event which might cause data loss.  Since this 
is a test environment I realize I have nothing to lose, but as always I 
appreciate the feedback.
 
John
 
 


      

Reply via email to