From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 121371] fsck created undeletable directory
Date: Thu, 07 Jul 2016 17:13:53 +0000 [thread overview]
Message-ID: <bug-121371-13602-avOJcJx0B8@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-121371-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=121371
Navin <navinp1912@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |navinp1912@gmail.com
--- Comment #6 from Navin <navinp1912@gmail.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.
next prev parent reply other threads:[~2016-07-07 17:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-03 15:41 [Bug 121371] New: fsck created undeletable directory bugzilla-daemon
2016-07-03 15:45 ` [Bug 121371] " bugzilla-daemon
2016-07-03 16:03 ` bugzilla-daemon
2016-07-03 18:38 ` bugzilla-daemon
2016-07-03 18:43 ` bugzilla-daemon
2016-07-04 10:46 ` bugzilla-daemon
2016-07-07 17:13 ` bugzilla-daemon [this message]
2016-07-10 13:58 ` bugzilla-daemon
2016-07-12 4:42 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-121371-13602-avOJcJx0B8@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-ext4@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).