View Single Post

   
  #1 (permalink)  
Old 01-05-2008, 12:14 PM
Friedhelm Neyer
 
Posts: n/a
Default fsck - strange behaviour

Hi

some days ago I have a damaged filesystem, a fsck -y /fs fails with the
message, that both superblocks where damaged and cannot be fixed (fs was
unmounted before fsck)
So I create a new filesystem, restore the files of the damaged fs into
the new one - no loss of data occurs.

But today I run a fsck -v against the damaged filesystem and got a
message that the superblock is valid.

Whats the heck is going on here, is there a difference between fsck -y
and fsck -v ?

Friedhelm
Reply With Quote