[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Thu, 07 Jul 2016 17:13:53 +0000
From: bugzilla-daemon@...zilla.kernel.org
To: linux-ext4@...r.kernel.org
Subject: [Bug 121371] fsck created undeletable directory
https://bugzilla.kernel.org/show_bug.cgi?id=121371
Navin <navinp1912@...il.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |navinp1912@...il.com
--- Comment #6 from Navin <navinp1912@...il.com> ---
Grief , your inode or directory content is empty. It is corrupted also. I got
this after fixing your #1589030 with debugfs and changing fields
directory permissions, flags to 0x1000 from your invalid value and also
changing the modify time stamp to current value from 2032.
I think this is a case where your inode field values has been corrupted or
overwritten due to some error/failure accidently. Fixing that or opening in
debugfs write mode solves the problem.
Please close this as it doesn't seem to be related to ext4 . If you can
reproduce this using a test case from standard utilities or other ways
accessing API's please submit the test case/code. You could go ahead and
dd/write a byte that changes some struct field in the ext4 and when broken.iso
is loaded it displays errors for one/few inodes. Unless done properly with
valid values , it is not supported i guess.
./1/plexus-component-annotations-1.5.5.jar.sha1:
total 8
drw-rw--w- 2 47469 268482890 4096 Nov 13 2014 .
drwxrwxr-x 3 47433 47433 4096 Jan 13 17:02 ..
./2:
total 12
drwxrwxrwx 3 root root 4096 Jul 7 22:31 .
drwxr-xr-x 5 root root 4096 Jul 3 20:21 ..
drwxrwxrwx 2 root root 4096 Jul 7 21:48 #1589030
./2/#1589030:
total 8
drwxrwxrwx 2 root root 4096 Jul 7 21:48 .
drwxrwxrwx 3 root root 4096 Jul 7 22:31 ..
./lost+found:
total 8
drwx------ 2 root root 4096 Jul 7 20:44 .
drwxr-xr-x 5 root root 4096 Jul 3 20:21 ..
--
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