similar to: XFS inode64 and Gluster 3.2.5 NFS export

Hi, I am trying to get the most out of my 40TB xfs file system and I have noticed that the inode64 mount option gives me a roughly 30% performance increase (besides the other useful things). The problem is that I have to export the filesystem via NFS and I cannot seem to get this working with the current version of nfs-utils (1.2.3). The export option fsid=uuid cannot be used (the standard

we recently deployed some large XFS file systems with centos 6.2 used as NFS servers... I've had some reports of a problem similar to the one reported here... http://www.linuxquestions.org/questions/red-hat-31/xfs-inode64-nfs-export-no_subtree_check-and-stale-nfs-file-handle-message-855844/ these reports are somewhat vague (third indirectly reported via internal corporate channels from

On 3/2/2015 11:56 AM, m.roth at 5-cent.us wrote: > Well, we got it working. However, the issue we're now worried about is > users creating files and subdirectories. Do we need to worry, and if so, > is there some way to reserve inodes < 32k table, other than creating tens > of thousands of dummy files now? > > We don't want, a year or two down the road, for this system

Hi all, I was recently poking more into the inode64 mount option for XFS filesystems. I seem to recall a comment that you could remount a filesystem with inode64, but then a colleague ran into issues where he did that but was still out of inodes. So, I did more research, and found this posting to the XFS list: http://oss.sgi.com/archives/xfs/2008-05/msg01409.html So for people checking the

Well, we got it working. However, the issue we're now worried about is users creating files and subdirectories. Do we need to worry, and if so, is there some way to reserve inodes < 32k table, other than creating tens of thousands of dummy files now? We don't want, a year or two down the road, for this system to be running, and suddenly everything's broken, because all lower inodes

John R Pierce wrote: > On 8/4/2015 7:14 AM, m.roth at 5-cent.us wrote: >> >> CentOS 6.6 (well, just updated with CR). I have some xfs filesystems >> on a RAID. They've been mounted with the option of defaults. Will it break >> the whole thing if I now change that to inode64, or was that something >> I needed to do when the fs was created, or is there some

Well, I've set up one of our new JetStors. xfs took *seconds* to put a filesystem on it. We're talking what df -h shows as 66TB. (Pardon me, my mind just SEGV'd on that statement....) Using bonnie++, I found that a) GPT and partitioning gave was insignificantly different than creating an xfs filesystem on a raw disk. I'm more comfortable with the partition, though.

Hi, I have Gluster 3.2.6 RPM's for Citrix XenServer 6.0. I've installed and mounted exports, but that's where I stopped. My issues are: 1. XenServer mounts the NFS servers SR subdirectory, not the export. Gluster won't do that. -- I can, apparently, mount the gluster export somewhere else, and then 'mount --bind' the subdir to the right place 2. I don't really know

Hi, Are there any proposed dates for a new release of Gluster? I'm currently running 3.3, and the gluster heal info commands all segfault. Gerald

Hi All, I have been trying out XFS given it is going to be the file system of choice from upstream in el7. Starting with an Adaptec ASR71605 populated with sixteen 4TB WD enterprise hard drives. The version of OS is 6.4 x86_64 and has 64G of RAM. This next part was not well researched as I had a colleague bothering me late on Xmas Eve that he needed 14 TB immediately to move data to from an

Hi, I'm currently running GlusterFS over XFS, and it works quite well. I'm wondering if it's possible to add data deduplication into the mix by: glusterfs --> lessfs --> xfs or glusterfs --> opendedupe --> xfs Has anybody tried doing this? We're running VM images on gluster, and I figure we could get a bit of space saving bu deduplicating the data. Gerald

On 8/4/2015 12:47 PM, James A. Peltier wrote: > Some older 32-bit software will likely have problems addressing any content outside of the 2^32 bit inode range. You will be able to see it, but reading and writing said data will likely be problematic The 99% of software that just does open,read,write will be fine regardless of word size. NFS is the only broken thing I ran into (on CentOS 6

----- Original Message ----- | John R Pierce wrote: | > On 8/4/2015 7:14 AM, m.roth at 5-cent.us wrote: | >> | >> CentOS 6.6 (well, just updated with CR). I have some xfs filesystems | >> on a RAID. They've been mounted with the option of defaults. Will it break | >> the whole thing if I now change that to inode64, or was that something | >> I needed to do

Hi, folks, CentOS 6.6 (well, just updated with CR). I have some xfs filesystems on a RAID. They've been mounted with the option of defaults. Will it break the whole thing if I now change that to inode64, or was that something I needed to do when the fs was created, or is there some conversion I can run that won't break everything? mark

----- Original Message ----- | On 8/4/2015 12:47 PM, James A. Peltier wrote: | > Some older 32-bit software will likely have problems addressing any content | > outside of the 2^32 bit inode range. You will be able to see it, but | > reading and writing said data will likely be problematic | | | The 99% of software that just does open,read,write will be fine | regardless of word size.

NFS needs a unique identifier for a filesystem to be able to export it. This can be set by the admin (fsid= in /etc/exports) but that is a hassle and it is best to set it automatically. nfs-utils currently uses the UUID returned by libblkid if that works, or the fsid returned by statfs64 if libblkid finds nothings and fsid is non-zero. Otherwise it uses device major/minor. This

Hi, I Configured 3 Clusters (For several Shared Homes between different maschines) .. So far no Problem. Now it need a Volume that going across this maschines, but the nodes are bound to there own clusters so peer probe fails . How i can build one big cluster with all nodes but without dataloss (And best without Downtime J) Hope there is some Pro that can help J Greets from Germany

m.roth at 5-cent.us wrote: > m.roth at 5-cent.us wrote: >> I'm exporting a directory, firewall's open on both machines (one CentOS >> 6.6, the other RHEL 6.6), it automounts on the exporting machine, but >> the >> other server, not so much. >> >> ls /mountpoint/directory eventually times out (directory being the NFS >> mount). mount -t nfs

Hi All, I have a very strange problem that I'm unable to pinpoint at the moment. For some reason I am simply unable to get xfs_quotas to report correctly on a freshly installed, fully patched CentOS 6 box. I have specified all the same options as on another machine which *is* reporting quota LABEL=TEST /exports/TEST xfs inode64,nobarrier,delaylog,usrquota,grpquota 0 0 xfs_quota -xc

I recently moved from the fuse client to NFS - Now I'm seeing a bunch of this in syslog. Is this something to be concerned about, or is it 'normal' NFS behavior? NFS: server localhost error: fileid changed fsid 0:15: expected fileid 0xd88ba88a97875981, got 0x40e476ef5fdfbe9f I also see a lot of 'stale file handle' in nfs.log, but the timestamps don't correspond.