Journal abortion in ext3 and its relation with remounting
kernel.shubham at gmail.com
Mon Jan 21 15:18:23 UTC 2013
I have RHEL-5.8 installed server.
Due to some inconsistent read write operation, ext3 journal got
corrupted and aborted but filesystem was not remounted read only.
In my understanding when there is ext3 journal has some corruption then
it should mount the filesystem read only .
So, I want to know in what cases this will not happen.
For unlinked inodes, I want to know the logic of handling unlinked
inodes in filesystem.
For an ex:
- Situation where unlinked inode will be found.
- How ext3 identifies unlinked inode ?
- What ext3 does when it sees an unlinked inode.
On 21-Jan-13 8:12 AM, Theodore Ts'o wrote:
> On Sun, Jan 20, 2013 at 07:39:24PM +0530, shubham wrote:
>> I was looking at the code of ext3 file system and found some strange
>> implementation there :
>> Can someone let me know the validity of below statements and with
>> reasoning :
>> 1. I found that it might also happen that journal is aborted but not
>> 2. Journal gets aborted but it might be possible to mount it in
>> read-write mode.
>> 3. Can we write some data on the partition where journal is aborted.
> Sorry, I'm not at all sure what you're asking. Can you go into more
> detail about what you're concerned about?
> Since I'm guessing English is not your first language, perhaps you can
> demonstrates with a series of commands which triggers what you think
> could happen? Or point at the explicit C code that for which you have
>> One more question, how unlinked inode is handled by ext3 ?
> Handled in what way? Again, what are you wondering about?
> - Ted
More information about the Ext3-users