[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Mon, 14 Dec 2009 14:46:10 GMT
From: bugzilla-daemon@...zilla.kernel.org
To: linux-ext4@...r.kernel.org
Subject: [Bug 14256] kernel BUG at fs/ext3/super.c:435
http://bugzilla.kernel.org/show_bug.cgi?id=14256
Jan Kara <jack@...e.cz> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |axboe@...nel.dk
--- Comment #15 from Jan Kara <jack@...e.cz> 2009-12-14 14:46:07 ---
Thanks for the debugging. So the problematic files were regular files that lead
pretty simple life - no references from unexpected places or so. What catches
my eye is that inode numbers are surprisingly small (22, 12, 13; in your
original report 17, 15). Since normal inode numbers start by 11 and that is
usually taken by lost+found, numbers 12 and 13 are as small as they can get. I
suppose this is a filesystem dedicated for the build, isn't it? And the files
making problems are created as a first files on that filesystem in its root
directory. Any idea what those files are?
Another thing: i_count=2501 for inode 22 is absurdly high. We'd have to leak
references really heavily for that file.
I've checked the code in writeback_inodes_wb() and wait_sb_inodes() but
reference counting there looks fine. So I have no clue what's going on right
now. Anyway, adding Jens to CC just in case it rings a bell to him.
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists