| View previous topic :: View next topic |
| Author |
Message |
humbletech99
Veteran
Joined: 26 May 2005
Posts: 1229
Location: London
|
 Posted: Tue May 23, 2006 11:50 am Post subject: [SOLVED] Ext3 filesystem "needs_recovery" flag |
 |
|
Hi,
I've got a large ext3 filesystem; when I do dumpe2fs /dev/sdb1 then I get the following line in the output:
| Code: | | Filesystem features: has_journal filetype needs_recovery |
but when I umount and fsck the filesystem it says the filesystem is clean:
| Code: | fsck /dev/sdb1
fsck 1.38 (30-Jun-2005)
e2fsck 1.38 (30-Jun-2005)
/dev/sdb1: clean, 60369/1098612736 files, 34497880/1098609399 blocks |
So I remounted it, dumpe2fsed it again and it had the same "needs_recovery" flag. I umounted it and ran dumpe2fs again and then it's needs_recovery flag was gone.
It would seem that ext3 works by placing this flag so if the filesystem isn't unmounted then the fsck happens, can anybody confirm this is correct?
_________________
The Human Equation:
value(geeks) > value(mundanes)
Last edited by humbletech99 on Tue May 23, 2006 2:15 pm; edited 1 time in total |
|
| Back to top |
|
 |
chrismortimore
l33t
Joined: 03 Dec 2005
Posts: 721
Location: Edinburgh, UK
|
| Posted: Tue May 23, 2006 1:04 pm Post subject: |
|
|
Thats what I've always thought.
Run "e2fsck -f /dev/sdb1" if you want to make sure your filesystem is OK.
_________________
Desktop: AMD Athlon64 3800+ Venice Core, 2GB PC3200, 2x160GB 7200rpm Maxtor DiamondMax 10, 2x320GB WD 7200rpm Caviar RE, Nvidia 6600GT 256MB
Laptop: Intel Pentium M, 512MB PC2700, 60GB 5400rpm IBM TravelStar, Nvidia 5200Go 64MB |
|
| Back to top |
|
|
troymc
Guru
Joined: 22 Mar 2006
Posts: 553
|
| Posted: Tue May 23, 2006 1:35 pm Post subject: |
|
|
That is correct.
The needs_recovery flag is cleared after a successful umount.
This is a failsafe, so, for example, if the box loses power the filesystem will be flagged.
troymc |
|
| Back to top |
|
|
humbletech99
Veteran
Joined: 26 May 2005
Posts: 1229
Location: London
|
| Posted: Tue May 23, 2006 2:15 pm Post subject: |
|
|
I did force a full fsck on it and it was fine, nothing wrong with the filesystem at all, which seems to confirm our belief that the flag is just there as a failsafe.
I'd really expect this to be hidden rather than in plain view, but that's the beauty of linux, it let's you understand...
thanks
_________________
The Human Equation:
value(geeks) > value(mundanes) |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Kernel & Hardware
