From: Curt Wohlgemuth <curtw@google.com>
To: Andrea Gelmini <andrea.gelmini@gmail.com>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: ext4_lookup: deleted inode referenced:
Date: Wed, 3 Feb 2010 11:14:52 -0800 [thread overview]
Message-ID: <6601abe91002031114v650a3f64m9c68796ca6a97e18@mail.gmail.com> (raw)
In-Reply-To: <9cdbb57f1002030819q4ce8dde8sbbaa3ed86b42f02d@mail.gmail.com>
On Wed, Feb 3, 2010 at 8:19 AM, Andrea Gelmini <andrea.gelmini@gmail.com> wrote:
> Hi all,
> since weeks sometimes I find this kind of warning in my dmesg:
>
> [43815.265473] EXT4-fs error (device dm-1): ext4_lookup: deleted inode
> referenced: 30889985
> [43815.267717] EXT4-fs error (device dm-1): ext4_lookup: deleted inode
> referenced: 30893057
> [43818.859494] EXT4-fs error (device dm-1): ext4_lookup: deleted inode
> referenced: 31550466
> [43826.212465] EXT4-fs error (device dm-1): ext4_lookup: deleted inode
> referenced: 31113765
>
> It happens both with stable and git kernel, on my home and backup
> partitions (the former on my laptop hd, the latter on external usb
> hd).
> I use them without journal and blocksize of 1K.
> After this I usually do a fsck (it runs without complains). Anyway,
> near one time per week, it comes back.
I have seen these as well, but running fsck has always fixed the issue.
Curt
> I can provide a dumpe2fs if you think it could be useuful.
>
> Thank a lot for your work and time,
> Andrea
> --
> To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2010-02-03 19:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-03 16:19 ext4_lookup: deleted inode referenced: Andrea Gelmini
2010-02-03 19:14 ` Curt Wohlgemuth [this message]
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=6601abe91002031114v650a3f64m9c68796ca6a97e18@mail.gmail.com \
--to=curtw@google.com \
--cc=andrea.gelmini@gmail.com \
--cc=linux-fsdevel@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).