linux-ext4 - [Bug 40822] EXT4-fs error (device dm-4): ext4_lookup:1044: inode #3308277: comm rm: deleted inode referenced: 3058008

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <bug-40822-13602-8Dm06dSrQg@https.bugzilla.kernel.org/>
Date:	Fri, 11 Apr 2014 12:33:49 +0000
From:	bugzilla-daemon@...zilla.kernel.org
To:	linux-ext4@...r.kernel.org
Subject: [Bug 40822] EXT4-fs error (device dm-4): ext4_lookup:1044: inode
 #3308277: comm rm: deleted inode referenced: 3058008

https://bugzilla.kernel.org/show_bug.cgi?id=40822

--- Comment #6 from Theodore Tso <tytso@....edu> ---
The fact that the first fsck had just summary accounting errors in pass 1, and
then a subsequent, back-to-back fsck showed errors in pass2, screams either (a)
some kind of hardware error, (b) the two mirrored copies of the RAID1 are out
of sync, or (c) someone or something else was modifying the filesytem at the
same time (i.e., the file system was mounted, and for some reason e2fsck's
safety checks didn't trigger, or it some other fsck or userspace program was
running at the same time, etc.)

I'm going to guess that (b) is the most likely, since this is a local
filesystem (i.e., you're not using fibre channel, or a remote block device, or
a dual-hosted SCSI arrangement or anything else exotic).   Could you try to
force a resync of the RAID mirrors, and then run another e2fsck -f check?

-- 
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