linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 187051] "orphan list check failed" error in ext4
Date: Mon, 07 Nov 2016 20:31:10 +0000	[thread overview]
Message-ID: <bug-187051-13602-ZDHJdA6Rba@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-187051-13602@https.bugzilla.kernel.org/>

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

Andreas Dilger <adilger.kernelbugzilla@dilger.ca> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |adilger.kernelbugzilla@dilg
                   |                            |er.ca

--- Comment #6 from Andreas Dilger <adilger.kernelbugzilla@dilger.ca> ---
(In reply to Theodore Tso from comment #3)
> So /usr/share/help/oc/totem/figures is a *directory*?    A directory has no
> business being on the orphan list, so something very strange is indeed going
> on.

It *is* possible to have a directory on the orphan list, since it is possible
to have an open-unlinked directory if one cd's into the directory before it is
unlinked (note nlink = 0, dtime is an inode number, not time):

    $ mkdir foo
    $ cd foo
    $ rmdir ../foo
    $ ls -lid .
    289432 drwxrwxr-x 0 mythtv mythtv 0 Nov  7 13:23 .
    $ sudo debugfs -c -R "stat <289432>" /dev/vg_basemyth/lvroot.basemyth 
    debugfs 1.42.7.wc2 (07-Nov-2013)
    Inode: 289432   Type: directory    Mode:  0775   Flags: 0x0
    Generation: 2752543570    Version: 0x00000000:00000002
    User:   500   Group:   500   Size: 4096
    File ACL: 0    Directory ACL: 0
    Links: 0   Blockcount: 8
    Fragment:  Address: 0    Number: 0    Size: 0
     ctime: 0x5820e2b5:4aa59b94 -- Mon Nov  7 13:23:17 2016
     atime: 0x5820e2b0:0048b0c8 -- Mon Nov  7 13:23:12 2016
     mtime: 0x5820e2b0:0048b0c8 -- Mon Nov  7 13:23:12 2016
    crtime: 0x5820e2b0:0048b0c8 -- Mon Nov  7 13:23:12 2016
     dtime: 0x0003f42b -- Sat Jan  3 16:58:35 1970
    Size of extra inode fields: 28
    BLOCKS:
    (0):1258994

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2016-11-07 20:31 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-05 20:27 [Bug 187051] New: "orphan list check failed" error in ext4 bugzilla-daemon
2016-11-06 23:48 ` [Bug 187051] " bugzilla-daemon
2016-11-07 10:40 ` bugzilla-daemon
2016-11-07 17:02 ` bugzilla-daemon
2016-11-07 17:50 ` bugzilla-daemon
2016-11-07 19:39 ` bugzilla-daemon
2016-11-07 20:31 ` bugzilla-daemon [this message]
2016-11-08 15:15 ` bugzilla-daemon
2017-01-28 12:25 ` bugzilla-daemon
2017-01-28 12:52 ` bugzilla-daemon
2017-01-29  5:09 ` bugzilla-daemon
2017-01-29  9:02 ` bugzilla-daemon
2017-01-29 10:00 ` bugzilla-daemon
2017-01-29 11:53 ` bugzilla-daemon
2017-01-29 11:56 ` bugzilla-daemon
2017-01-29 11:56 ` bugzilla-daemon
2017-01-29 11:59 ` bugzilla-daemon
2017-01-30  2:21 ` bugzilla-daemon
2017-01-30 15:24 ` bugzilla-daemon
2017-08-28 11:57 ` bugzilla-daemon
2017-10-03 22:44 ` bugzilla-daemon
2017-10-04 12:35 ` bugzilla-daemon
2017-10-05  2:27 ` bugzilla-daemon
2017-10-05 11:00 ` 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-187051-13602-ZDHJdA6Rba@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).