Re: R: nfs cluster, problem with delete file in the failover case

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, May 13, 2015 at 07:38:03PM +0000, gianpietro sella wrote:
> J. Bruce Fields <bfields <at> fieldses.org> writes:
> 
> > 
> > On Wed, May 13, 2015 at 01:06:17PM +0200, sella gianpietro wrote:
> > > this is the inodes number in the exported folder of the volume 
> > > in the server before write file in the client:
> > > 
> > > [root <at> cld-blu-13 nova]# du --inodes
> > > 2       .
> > > 
> > > this is the used block:
> > > 
> > > [root <at> cld-blu-13 nova]# df -T
> > > Filesystem                            Type      1K-blocks    Used  Available
> > > Use% Mounted on
> > > /dev/mapper/nfsclustervg-nfsclusterlv xfs      1152878588   33000 1152845588
> > > 1% /nfscluster
> > > 
> > > after write file in the client with umount/mount during writing:
> > > 
> > > [root <at> cld-blu-13 nova]# du --inodes
> > > 3       .
> > > 
> > > [root <at> cld-blu-13 nova]# df -T
> > > Filesystem                            Type      1K-blocks     Used
> > > Available Use% Mounted on
> > > /dev/mapper/nfsclustervg-nfsclusterlv xfs      1152878588 21004520
> > > 1131874068   2% /nfscluster
> > > 
> > > thi is correct.
> > > now delete file:
> > > 
> > > [root <at> cld-blu-13 nova]# du --inodes
> > > 2       .
> > > 
> > > the number of the inodes is correct (from 3 to 2).
> > > 
> > > [root <at> cld-blu-13 nova]# df -T
> > > Filesystem                            Type      1K-blocks     Used
> > > Available Use% Mounted on
> > > /dev/mapper/nfsclustervg-nfsclusterlv xfs      1152878588 21004520
> > > 1131874068   2% /nfscluster
> > > 
> > > the number of used block is not correct.
> > > Do not return to initial value 33000
> > 
> > If you try "df -i", you'll probably also find that it gives the "wrong"
> > result.  (So, probably 3 inodes, though "du --inodes" is still only
> > finding 2).
> > 
> > --b.
> > 
> 
> 
> the problem is that after delete file the inode go in the orphaned state:

Yeah, that's consistent with everything else--we're not removing a
dentry when we should for some reason, so the inode's staying
referenced.

--b.

> 
> [root@cld-blu-13 nova]# tune2fs -l /dev/nfsclustervg/nfsclusterlv |grep -i inode
> Filesystem features:      has_journal ext_attr resize_inode dir_index
> filetype needs_recovery sparse_super large_file
> Inode count:              72097792
> Free inodes:              72097754
> Inodes per group:         8192
> Inode blocks per group:   512
> First inode:              11
> Inode size:               256
> Journal inode:            8
> First orphan inode:       53067783
> Journal backup:           inode blocks
> 
> 
> 
> 
> -- 
> Linux-cluster mailing list
> Linux-cluster@xxxxxxxxxx
> https://www.redhat.com/mailman/listinfo/linux-cluster

-- 
Linux-cluster mailing list
Linux-cluster@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/linux-cluster




[Index of Archives]     [Corosync Cluster Engine]     [GFS]     [Linux Virtualization]     [Centos Virtualization]     [Centos]     [Linux RAID]     [Fedora Users]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite Camping]

  Powered by Linux