linux-nilfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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: Tue, 8 Feb 2011 21:32:37 +0100	[thread overview]
Message-ID: <20110208213237.0a0bef59@micro24> (raw)
In-Reply-To: <20110208.204230.73657026.ryusuke-sG5X7nlA6pw@public.gmane.org>

Le Tue, 08 Feb 2011 20:42:30 +0900 (JST),
Ryusuke Konishi <ryusuke-sG5X7nlA6pw@public.gmane.org> a écrit :

> Hi,
> 
> Thank you for the detail report!  It's really helpful.
> 
> I understood the zero link count inode was causing a chain reaction.
> 
> And the inode in question at cp15731 also seems to be overridden
> because gid, size, and timestamp all differs from that file at
> cp15730.
> 
> > cp15730
> > -------
> > mnt/snap5/cut:
> > total 4
> > 14 -rw-r--r-- 1 philippe 1000 47 25 janv. 22:33
> > f5_20110125_202053.ts(0).Xcl
> 
> > cp15731
> > -------
> > mnt/snap7/cut:
> > total 9223372036848683032
> > 14 -rw-r--r-- 0 philippe users 6214528000 24 janv. 01:30
> > f5_20110125_202053.ts(0).Xcl
> 
> Can't you find another file with the inode number 14 in the snapshot
> cp15731 or cp15730 ?
> 
> I reviewed back unlink() implementation, but haven't found any issues
> so far.  The problem may be rooted much deeper.
> 
> 'stat' command may give us much information than 'ls -l' in this case.

Hi,
in my previous mail, ls -li ** give all the files in the filesystem (directory capture has inode 12 and cut 13). In
cp15730 and cp15731, there's only one file with inode 14.

Heres's the 3 stat outputs :
philippe@micro11:~$ sudo mount -t nilfs2 -r -o cp=15730 /dev/mapper/vg11a-video mnt/snap5
philippe@micro11:~$ sudo mount -t nilfs2 -r -o cp=15731 /dev/mapper/vg11a-video mnt/snap6
philippe@micro11:~$ sudo mount -t nilfs2 -r -o cp=15732 /dev/mapper/vg11a-video mnt/snap7

philippe@micro11:~$ stat mnt/snap5/cut/f5_20110125_202053.ts\(0\).Xcl 
  File: « mnt/snap5/cut/f5_20110125_202053.ts(0).Xcl »
  Size: 47        	Blocks: 8          IO Block: 4096   fichier
Device: fe00h/65024d	Inode: 14          Links: 1
Access: (0644/-rw-r--r--)  Uid: ( 1000/philippe)   Gid: ( 1000/ UNKNOWN)
Access: 2011-01-25 22:33:34.914556435 +0100
Modify: 2011-01-25 22:33:34.914556435 +0100
Change: 2011-01-25 22:33:34.914556435 +0100
 Birth: -

philippe@micro11:~$ stat mnt/snap6/cut/f5_20110125_202053.ts\(0\).Xcl
  File: « mnt/snap6/cut/f5_20110125_202053.ts(0).Xcl »
  Size: 6214528000	Blocks: 18446744073697366064 IO Block: 4096   fichier
Device: fe00h/65024d	Inode: 14          Links: 0
Access: (0644/-rw-r--r--)  Uid: ( 1000/philippe)   Gid: (  100/   users)
Access: 2011-01-24 01:30:02.260271565 +0100
Modify: 2011-01-24 01:30:02.260271565 +0100
Change: 2011-01-25 20:28:48.894851740 +0100
 Birth: -

  File: « mnt/snap7/cut/f5_20110125_202053.ts(0).Xcl »
  Size: 0         	Blocks: 0          IO Block: 4096   fichier vide
Device: fe00h/65024d	Inode: 14          Links: 1
Access: (0644/-rw-r--r--)  Uid: ( 1000/philippe)   Gid: (  100/   users)
Access: 2011-01-29 18:19:51.719138031 +0100
Modify: 2011-01-29 18:19:51.719138031 +0100
Change: 2011-01-29 18:19:51.719138031 +0100
 Birth: -

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

  parent reply	other threads:[~2011-02-08 20:32 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 [this message]
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=20110208213237.0a0bef59@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).