From: Philippe CHATAIGNON <liste-ZXOCcuNttmoBe96aLqz0jA@public.gmane.org>
To: linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Bug : reuse same inode
Date: Sun, 6 Feb 2011 20:09:28 +0100 [thread overview]
Message-ID: <20110206200928.633fa00c@micro24> (raw)
Hi all,
I use nilfs2 on a lvm partition for recording dvb streams : it creates
big files and I often deleted them quickly so there only a few files on the partition.
Today I notice a problem : where a new file were created, it takes the same inode that a file already have.
So the previous file were lost, like if an hard link was made.
philippe@micro11:~$ ls -li $v
total 30051016
14 -rw-r--r-- 1 philippe users 93849600 6 févr. 14:51 f2_20110130_174456.ts
16 -rw-r--r-- 1 philippe users 8606489600 9 janv. 15:42 f3_20110107_205154.ts
14 -rw-r--r-- 1 philippe users 93849600 6 févr. 14:51 f3_20110206_144851.ts
19 -rw-r--r-- 1 philippe users 10623052800 6 févr. 19:55 f3_20110206_145141.ts
15 -rw-r--r-- 1 philippe users 4688870400 19 janv. 23:14 f4_20110119_204007.ts
The file created today is f3_20110206_144851.ts : it reuse inode 14
that the file f2_20110130_174456.ts already had. On the third column, you can see there
is only one link (and not 2 as if ln was used).
Of course, I can use a snapshot to recover the old file (f2_20110130_174456.ts).
philippe@micro11:~$ ls mnt/snap2/capture -li
total 32584848
20 -rw-r--r-- 1 philippe users 4812800 5 févr. 17:43 canal_20110205_172318.ts
14 -rw-r--r-- 0 philippe users 13390412800 31 janv. 01:00 f2_20110130_174456.ts
16 -rw-r--r-- 1 philippe users 8606489600 9 janv. 15:42 f3_20110107_205154.ts
15 -rw-r--r-- 1 philippe users 4688870400 19 janv. 23:14 f4_20110119_204007.ts
I run Archlinux x86_64 on 2.6.37. It's my first bug report.
Ask me for additionnal information if I could help.
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 reply other threads:[~2011-02-06 19:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-06 19:09 Philippe CHATAIGNON [this message]
2011-02-07 4:02 ` Bug : reuse same inode 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
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=20110206200928.633fa00c@micro24 \
--to=liste-zxoccunttmobe96alqz0ja@public.gmane.org \
--cc=linux-nilfs-u79uwXL29TY76Z2rM5mHXA@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).