From: Philippe CHATAIGNON <liste-ZXOCcuNttmoBe96aLqz0jA@public.gmane.org>
To: Ryusuke Konishi <ryusuke-sG5X7nlA6pw@public.gmane.org>
Cc: linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Bug : reuse same inode
Date: Fri, 18 Feb 2011 20:57:39 +0100 [thread overview]
Message-ID: <20110218205739.26dde3b8@micro24> (raw)
In-Reply-To: <20110218.162145.57461053.ryusuke-sG5X7nlA6pw@public.gmane.org>
Le Fri, 18 Feb 2011 16:21:45 +0900 (JST),
Ryusuke Konishi <ryusuke-sG5X7nlA6pw@public.gmane.org> a écrit :
> Thank you for the cooperation.
>
> Yeah, this file is exactly the file that overrode
> "f5_20110125_202053.ts(0).Xcl" at cp15731.
>
> I don't know why the past inode overrode the latest inode. One
> possible explanation is that garbage collection caused this
> interference, and another is interference by a snapshot mount for the
> checkpoint 14444.
>
> Were you mounting the snapshot cp14444 when
> "f5_20110125_202053.ts(0).Xcl" was destroyed at cp15731 ?
>
> If not, dummy on-memory inodes used for the garbage collection seem
> suspicious to me.
Hi,
the first time I used snapshot on this fs is when I lost a file
because of inode's reuse (my first mail). When file f5_...Xcl was
deleted at cp15731, cp14444 was not a ss and wasn't mounted. And there
were no ss on this fs (only cp).
Tell me if you need additional information. This partition's size is
200G and I'll need that space in a few days.
Regards,
PhC
--
To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-02-18 19:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-06 19:09 Bug : reuse same inode Philippe CHATAIGNON
2011-02-07 4:02 ` Ryusuke Konishi
[not found] ` <20110207.130214.221723444.ryusuke-sG5X7nlA6pw@public.gmane.org>
2011-02-07 19:42 ` Philippe CHATAIGNON
2011-02-08 11:42 ` Ryusuke Konishi
[not found] ` <20110208.204230.73657026.ryusuke-sG5X7nlA6pw@public.gmane.org>
2011-02-08 20:32 ` Philippe CHATAIGNON
2011-02-10 5:01 ` Ryusuke Konishi
[not found] ` <20110210.140105.33383103.ryusuke-sG5X7nlA6pw@public.gmane.org>
2011-02-10 22:32 ` Philippe CHATAIGNON
2011-02-18 7:21 ` Ryusuke Konishi
[not found] ` <20110218.162145.57461053.ryusuke-sG5X7nlA6pw@public.gmane.org>
2011-02-18 19:57 ` Philippe CHATAIGNON [this message]
2011-02-19 13:22 ` Ryusuke Konishi
[not found] ` <20110219.222232.05855196.ryusuke-sG5X7nlA6pw@public.gmane.org>
2011-02-19 15:26 ` Philippe CHATAIGNON
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=20110218205739.26dde3b8@micro24 \
--to=liste-zxoccunttmobe96alqz0ja@public.gmane.org \
--cc=linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=ryusuke-sG5X7nlA6pw@public.gmane.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).