what causes dirty inodes

[jpn1]

we rebooted a system and a LV didn't come back on line. I ran an fsck -y on the un-mounted volume and it fixed all kinds of things. After it finished it mounted fine and we could get the data.

What causes these file system problems dirty inodes and bad superblocks.
I thought dirty inodes were buffers that were waiting to be written, if so and I rebooted the box wouldn't there be some data loss??

 

[khalidaaa]

While googling i found this link (taking about VERITAS filesystem)

http://seer.entsupport.symantec.com/docs/247040.htm

I can see that it says one of the reasons is

after a reboot, JFS/JFS2 file systems will not mount if the file system is marked dirty due to incorrect shutdown or need for JFS log replay

Regards,
Khalid