* Run out of inodes?
@ 2014-08-29 10:08 Samuel Granjeaud
2014-08-29 11:43 ` Emmanuel Florac
2014-08-29 11:48 ` Brian Foster
0 siblings, 2 replies; 10+ messages in thread
From: Samuel Granjeaud @ 2014-08-29 10:08 UTC (permalink / raw)
To: xfs
Hi,
Sorry if the answer is obvious, but I didn't find any clear answer after
googling.
I have a XFS system of 18T over LVM. Recently, I could not create new
files or directories.
# mkdir tempo
mkdir: cannot create directory `tempo': No space left on device
After deleting a few files, this command runs successfully.
So I think that the system runs out of something, inodes I guess.
But the df diagnosis does not enlight it: only 1% used.
# df -ht xfs
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/vg1_backup-backup
18T 12T 6.6T 63% /mnt/vg1_backup/backup
# df -it xfs
Filesystem Inodes IUsed IFree IUse% Mounted on
/dev/mapper/vg1_backup-backup
18874040320 530042 18873510278 1%
/mnt/vg1_backup/backup
So what is wrong? How should I solve the problem?
I read about xfs_grow -m, but I am not sure if it could help.
Of course, I rebooted the system before my trials.
Best regards,
Samuel
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
^ permalink raw reply [flat|nested] 10+ messages in thread* Re: Run out of inodes? 2014-08-29 10:08 Run out of inodes? Samuel Granjeaud @ 2014-08-29 11:43 ` Emmanuel Florac 2014-08-29 11:48 ` Brian Foster 1 sibling, 0 replies; 10+ messages in thread From: Emmanuel Florac @ 2014-08-29 11:43 UTC (permalink / raw) To: Samuel Granjeaud; +Cc: xfs Le Fri, 29 Aug 2014 12:08:08 +0200 Samuel Granjeaud <samuel.granjeaud@inserm.fr> écrivait: > I have a XFS system of 18T over LVM. Recently, I could not create new > files or directories. What is the distribution, the kernel version (uname -a)? What are the mount options? Maybe the FS has been mounted with inode64 as an option at some point in time, but isn't anymore? -- ------------------------------------------------------------------------ Emmanuel Florac | Direction technique | Intellique | <eflorac@intellique.com> | +33 1 78 94 84 02 ------------------------------------------------------------------------ _______________________________________________ xfs mailing list xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: Run out of inodes? 2014-08-29 10:08 Run out of inodes? Samuel Granjeaud 2014-08-29 11:43 ` Emmanuel Florac @ 2014-08-29 11:48 ` Brian Foster 2014-08-29 13:29 ` Samuel Granjeaud 1 sibling, 1 reply; 10+ messages in thread From: Brian Foster @ 2014-08-29 11:48 UTC (permalink / raw) To: Samuel Granjeaud; +Cc: xfs On Fri, Aug 29, 2014 at 12:08:08PM +0200, Samuel Granjeaud wrote: > Hi, > > Sorry if the answer is obvious, but I didn't find any clear answer after > googling. > > I have a XFS system of 18T over LVM. Recently, I could not create new files > or directories. > > # mkdir tempo > mkdir: cannot create directory `tempo': No space left on device > > After deleting a few files, this command runs successfully. > > So I think that the system runs out of something, inodes I guess. > > But the df diagnosis does not enlight it: only 1% used. > > # df -ht xfs > Filesystem Size Used Avail Use% Mounted on > /dev/mapper/vg1_backup-backup > 18T 12T 6.6T 63% /mnt/vg1_backup/backup > # df -it xfs > Filesystem Inodes IUsed IFree IUse% Mounted on > /dev/mapper/vg1_backup-backup > 18874040320 530042 18873510278 1% > /mnt/vg1_backup/backup > > So what is wrong? How should I solve the problem? > > I read about xfs_grow -m, but I am not sure if it could help. > Of course, I rebooted the system before my trials. > You should probably include more information for context: http://xfs.org/index.php/XFS_FAQ#Q:_What_information_should_I_include_when_reporting_a_problem.3F That aside... is inode64 enabled? Is imaxpct set to a non-default value? Also, how is this filesystem used? I notice it's named as some kind of backup volume. Brian > Best regards, > Samuel > > > _______________________________________________ > xfs mailing list > xfs@oss.sgi.com > http://oss.sgi.com/mailman/listinfo/xfs _______________________________________________ xfs mailing list xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: Run out of inodes? 2014-08-29 11:48 ` Brian Foster @ 2014-08-29 13:29 ` Samuel Granjeaud 2014-08-29 15:02 ` Eric Sandeen 0 siblings, 1 reply; 10+ messages in thread From: Samuel Granjeaud @ 2014-08-29 13:29 UTC (permalink / raw) To: xfs Taking into account the two answers, here is some more information. The system is a openfiler installation, v2.3, up-to-date. https://www.openfiler.com/community/download The problematic system is a backup but the production system uses the same openfiler NAS system. The difference is that there are currently more files on the backup system than the production system; so I guess the problem will appear sooner on the prod sys. # xfs_info /dev/vg1_backup/backup meta-data=/mnt/vg1_backup/backup isize=256 agcount=80, agsize=58981376 blks = sectsz=512 data = bsize=4096 blocks=4718510080, imaxpct=25 = sunit=0 swidth=0 blks, unwritten=1 naming =version 2 bsize=4096 log =internal bsize=4096 blocks=32768, version=1 = sectsz=512 sunit=0 blks realtime =none extsz=65536 blocks=0, rtextents=0 # uname -a Linux 2.6.26.8-1.0.11.smp.gcc3.4.x86_64 #1 SMP Sun Jan 11 02:42:55 GMT 2009 x86_64 x86_64 x86_64 GNU/Linux # xfs_info -V /dev/vg1_backup/backup xfs_info version 2.6.25 # cat /etc/fstab ... /dev/vg1/pcurrent /mnt/vg1/pcurrent xfs defaults,usrquota,grpquota 0 0 # cat /etc/mtab ... /dev/mapper/vg1-pcurrent /mnt/vg1/pcurrent xfs rw,usrquota,grpquota 0 0 # lvm version LVM version: 2.02.34 (2008-04-10) Library version: 1.02.24 (2007-12-20) Driver version: 4.13.0 ]# more /proc/meminfo /proc/mounts /proc/partitions :::::::::::::: /proc/meminfo :::::::::::::: MemTotal: 2057876 kB MemFree: 18808 kB Buffers: 3868 kB Cached: 1906736 kB SwapCached: 160 kB Active: 581108 kB Inactive: 1367680 kB SwapTotal: 1028152 kB SwapFree: 1027848 kB Dirty: 156 kB Writeback: 0 kB AnonPages: 38168 kB Mapped: 34376 kB Slab: 67104 kB SReclaimable: 55772 kB SUnreclaim: 11332 kB PageTables: 4112 kB NFS_Unstable: 0 kB Bounce: 0 kB WritebackTmp: 0 kB CommitLimit: 2057088 kB Committed_AS: 105580 kB VmallocTotal: 34359738367 kB VmallocUsed: 272688 kB VmallocChunk: 34359465359 kB HugePages_Total: 0 HugePages_Free: 0 HugePages_Rsvd: 0 HugePages_Surp: 0 Hugepagesize: 2048 kB :::::::::::::: /proc/mounts :::::::::::::: rootfs / rootfs rw 0 0 /dev /dev tmpfs rw,mode=755 0 0 /dev/root / ext3 rw,errors=continue,data=ordered 0 0 /proc /proc proc rw 0 0 /proc/bus/usb /proc/bus/usb usbfs rw 0 0 /sys /sys sysfs rw 0 0 devpts /dev/pts devpts rw,gid=5,mode=620 0 0 /dev/sda1 /boot ext3 rw,errors=continue,data=ordered 0 0 tmpfs /dev/shm tmpfs rw 0 0 /dev/vg1/pcurrent /mnt/vg1/pcurrent xfs rw,attr2,nobarrier,usrquota,prjquota,grpquota 0 0 none /proc/sys/fs/binfmt_misc binfmt_misc rw 0 0 sunrpc /var/lib/nfs/rpc_pipefs rpc_pipefs rw 0 0 :::::::::::::: /proc/partitions :::::::::::::: major minor #blocks name 8 0 3145728 sda 8 1 104391 sda1 8 2 2008125 sda2 8 3 1028160 sda3 8 16 1887436800 sdb 8 17 1887436656 sdb1 8 32 1887436800 sdc 8 33 1887436656 sdc1 8 48 1887436800 sdd 8 49 1887436656 sdd1 8 64 1887436800 sde 8 65 1887436656 sde1 8 80 1887436800 sdf 8 81 1887436656 sdf1 8 96 1887436800 sdg 8 97 1887436656 sdg1 8 112 1887436800 sdh 8 113 1887436656 sdh1 8 128 1887436800 sdi 8 129 1887436656 sdi1 8 144 1887436800 sdj 8 145 1887436656 sdj1 8 160 1887436800 sdk 8 161 1887436656 sdk1 8 176 655360000 sdl 8 177 655355578 sdl1 253 0 18874040320 dm-0 The system is a ESXi virtual machine. RAID is hardware, managed at the BIOS level. Disks are DELL SATA. I have no idea concerning the inode64 option. Just tell me how to find it out. I don't think this option was changed: as previously told, removing a few files allows files to be created without error. I could add some more information if needed. Thanks for your help, Samuel _______________________________________________ xfs mailing list xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: Run out of inodes? 2014-08-29 13:29 ` Samuel Granjeaud @ 2014-08-29 15:02 ` Eric Sandeen 2014-08-29 15:22 ` Samuel Granjeaud 2014-08-30 19:33 ` Samuel GRANJEAUD IR/INSERM 0 siblings, 2 replies; 10+ messages in thread From: Eric Sandeen @ 2014-08-29 15:02 UTC (permalink / raw) To: Samuel Granjeaud, xfs On 8/29/14, 8:29 AM, Samuel Granjeaud wrote: > Taking into account the two answers, here is some more information. > > The system is a openfiler installation, v2.3, up-to-date. > https://www.openfiler.com/community/download > > The problematic system is a backup but the production system uses the same openfiler NAS system. The difference is that there are currently more files on the backup system than the production system; so I guess the problem will appear sooner on the prod sys. > > # xfs_info /dev/vg1_backup/backup > meta-data=/mnt/vg1_backup/backup isize=256 agcount=80, agsize=58981376 blks > = sectsz=512 > data = bsize=4096 blocks=4718510080, imaxpct=25 > = sunit=0 swidth=0 blks, unwritten=1 > naming =version 2 bsize=4096 > log =internal bsize=4096 blocks=32768, version=1 > = sectsz=512 sunit=0 blks > realtime =none extsz=65536 blocks=0, rtextents=0 > > # uname -a > Linux 2.6.26.8-1.0.11.smp.gcc3.4.x86_64 #1 SMP Sun Jan 11 02:42:55 GMT 2009 x86_64 x86_64 x86_64 GNU/Linux > > # xfs_info -V /dev/vg1_backup/backup > xfs_info version 2.6.25 > > # cat /etc/fstab > ... > /dev/vg1/pcurrent /mnt/vg1/pcurrent xfs defaults,usrquota,grpquota 0 0 > > # cat /etc/mtab > ... > /dev/mapper/vg1-pcurrent /mnt/vg1/pcurrent xfs rw,usrquota,grpquota 0 0 <thanks for all the extra info> > I have no idea concerning the inode64 option. Just tell me how to find it out. I don't think this option was changed: as previously told, removing a few files allows files to be created without error. You'll want to be using the inode64 mount option for this filesystem; I'm surprised the openfiler folks didn't do this by default. http://xfs.org/index.php/XFS_FAQ#Q:_What_is_the_inode64_mount_option_for.3F add it to fstab for this filesystem, reboot the box (or unmount/mount the filesystem) and all should be well. -Eric _______________________________________________ xfs mailing list xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: Run out of inodes? 2014-08-29 15:02 ` Eric Sandeen @ 2014-08-29 15:22 ` Samuel Granjeaud 2014-08-30 19:33 ` Samuel GRANJEAUD IR/INSERM 1 sibling, 0 replies; 10+ messages in thread From: Samuel Granjeaud @ 2014-08-29 15:22 UTC (permalink / raw) To: xfs Eric Sandeen wrote, On 29/08/14 17:02: > > You'll want to be using the inode64 mount option for this filesystem; I'm surprised the openfiler folks didn't do this by default. > > http://xfs.org/index.php/XFS_FAQ#Q:_What_is_the_inode64_mount_option_for.3F Well, I am using the 2.3 version; may be the 2.99 version does it. > add it to fstab for this filesystem, reboot the box (or unmount/mount the filesystem) and all should be well. I added the option and rebooted the system. A short rsync ran successfully, but it may not have exhausted the pool of previously released inodes. Tonight a bigger rsync will take place and I will let you know the result. Thanks for pointing me this option, that I hesitated to apply. _______________________________________________ xfs mailing list xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: Run out of inodes? 2014-08-29 15:02 ` Eric Sandeen 2014-08-29 15:22 ` Samuel Granjeaud @ 2014-08-30 19:33 ` Samuel GRANJEAUD IR/INSERM 2014-08-31 2:46 ` Eric Sandeen 2014-09-01 19:19 ` Emmanuel Florac 1 sibling, 2 replies; 10+ messages in thread From: Samuel GRANJEAUD IR/INSERM @ 2014-08-30 19:33 UTC (permalink / raw) To: xfs Enabling the inode64 option has solved the problem. Final question: could some issues appear with SAMBA? # smbstatus -V Version 3.4.5 # xfs_info -V /dev/vg1_backup/backup xfs_info version 2.6.25 # uname -a Linux 2.6.26.8-1.0.11.smp.gcc3.4.x86_64 #1 SMP Sun Jan 11 02:42:55 GMT 2009 x86_64 x86_64 x86_64 GNU/Linux Thanks for your expert help. Best regards, Samuel On 29-08-2014 17:02, Eric Sandeen wrote: > > You'll want to be using the inode64 mount option for this filesystem; > I'm surprised the openfiler folks didn't do this by default. > > http://xfs.org/index.php/XFS_FAQ#Q:_What_is_the_inode64_mount_option_for.3F > > add it to fstab for this filesystem, reboot the box (or unmount/mount > the filesystem) and all should be well. > > -Eric _______________________________________________ xfs mailing list xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: Run out of inodes? 2014-08-30 19:33 ` Samuel GRANJEAUD IR/INSERM @ 2014-08-31 2:46 ` Eric Sandeen 2014-09-01 19:19 ` Emmanuel Florac 1 sibling, 0 replies; 10+ messages in thread From: Eric Sandeen @ 2014-08-31 2:46 UTC (permalink / raw) To: Samuel GRANJEAUD IR/INSERM, xfs On 8/30/14, 2:33 PM, Samuel GRANJEAUD IR/INSERM wrote: > Enabling the inode64 option has solved the problem. > > Final question: could some issues appear with SAMBA? ah, what sort of issues? Any application which uses i.e. a 32-bit stat() interface will return -EOVERFLOW on a 64-bit inode. http://sandeen.net/wordpress/computers/the-world-wants-32-bit-inodes/ http://blog.fmeh.org/2013/05/11/does-the-world-need-32-bit-inodes/ -Eric _______________________________________________ xfs mailing list xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: Run out of inodes? 2014-08-30 19:33 ` Samuel GRANJEAUD IR/INSERM 2014-08-31 2:46 ` Eric Sandeen @ 2014-09-01 19:19 ` Emmanuel Florac 2014-09-02 7:22 ` Samuel Granjeaud 1 sibling, 1 reply; 10+ messages in thread From: Emmanuel Florac @ 2014-09-01 19:19 UTC (permalink / raw) To: Samuel GRANJEAUD IR/INSERM; +Cc: xfs Le Sat, 30 Aug 2014 21:33:46 +0200 vous écriviez: > Final question: could some issues appear with SAMBA? > > # smbstatus -V > Version 3.4.5 Is your whole distribution 64 bits, or only the kernel? However, I've never had any problem with samba, but some with NFS. -- ------------------------------------------------------------------------ Emmanuel Florac | Direction technique | Intellique | <eflorac@intellique.com> | +33 1 78 94 84 02 ------------------------------------------------------------------------ _______________________________________________ xfs mailing list xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: Run out of inodes? 2014-09-01 19:19 ` Emmanuel Florac @ 2014-09-02 7:22 ` Samuel Granjeaud 0 siblings, 0 replies; 10+ messages in thread From: Samuel Granjeaud @ 2014-09-02 7:22 UTC (permalink / raw) To: xfs Thanks Eric and Emmanuel. Here are the diagnosis of the installed samba distrib with openfiler 64 bits # smb (auto-completion key) smbcontrol smbd smbpasswd smbprint smbstatus smbtar # which smbcontrol smbd smbpasswd smbprint smbstatus smbtar /usr/bin/smbcontrol /usr/sbin/smbd /usr/bin/smbpasswd /usr/bin/smbprint /usr/bin/smbstatus /usr/bin/smbtar # file /usr/sbin/smbd /usr/bin/smb* /usr/sbin/smbd: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), for GNU/Linux 2.4.0, stripped /usr/bin/smbcontrol: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), for GNU/Linux 2.4.0, stripped /usr/bin/smbpasswd: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), for GNU/Linux 2.4.0, stripped /usr/bin/smbprint: Bourne shell script text executable /usr/bin/smbstatus: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), for GNU/Linux 2.4.0, stripped /usr/bin/smbtar: Bourne shell script text executable [root@proteo-replica ~]# ldd /usr/sbin/smbd /usr/bin/smb* /usr/sbin/smbd: libldap-2.2.so.7 => /usr/lib64/libldap-2.2.so.7 (0x00007fe4c97ff000) liblber-2.2.so.7 => /usr/lib64/liblber-2.2.so.7 (0x00007fe4c96f0000) libgssapi_krb5.so.2 => /usr/kerberos/lib64/libgssapi_krb5.so.2 (0x00007fe4c95d8000) libkrb5.so.3 => /usr/kerberos/lib64/libkrb5.so.3 (0x00007fe4c945e000) libk5crypto.so.3 => /usr/kerberos/lib64/libk5crypto.so.3 (0x00007fe4c933a000) libkrb5support.so.0 => /usr/kerberos/lib64/libkrb5support.so.0 (0x00007fe4c9237000) libcom_err.so.3 => /usr/kerberos/lib64/libcom_err.so.3 (0x00007fe4c9133000) libresolv.so.2 => /lib64/libresolv.so.2 (0x00007fe4c9020000) libcrypt.so.1 => /lib64/libcrypt.so.1 (0x00007fe4c8eed000) libpam.so.0 => /lib64/libpam.so.0 (0x00007fe4c8de5000) libacl.so.1 => /lib64/libacl.so.1 (0x00007fe4c8cdd000) libattr.so.1 => /lib64/libattr.so.1 (0x00007fe4c8bd9000) libcap.so.1 => /lib64/libcap.so.1 (0x00007fe4c8ad5000) libnsl.so.1 => /lib64/libnsl.so.1 (0x00007fe4c89bf000) libdl.so.2 => /lib64/libdl.so.2 (0x00007fe4c88bc000) librt.so.1 => /lib64/tls/librt.so.1 (0x00007fe4c87a2000) libpopt.so.0 => /usr/lib64/libpopt.so.0 (0x00007fe4c869a000) libtalloc.so.1 => /usr/lib64/libtalloc.so.1 (0x00007fe4c8592000) libtdb.so.1 => /usr/lib64/libtdb.so.1 (0x00007fe4c8485000) libwbclient.so.0 => /usr/lib64/libwbclient.so.0 (0x00007fe4c8379000) libz.so.1 => /usr/lib64/libz.so.1 (0x00007fe4c8264000) libc.so.6 => /lib64/tls/libc.so.6 (0x00007fe4c803e000) libsasl2.so.2 => /usr/lib64/libsasl2.so.2 (0x00007fe4c7f27000) libssl.so.5 => /lib64/libssl.so.5 (0x00007fe4c7dde000) libcrypto.so.5 => /lib64/libcrypto.so.5 (0x00007fe4c7b6e000) /lib64/ld-linux-x86-64.so.2 (0x00007fe4c9935000) libpthread.so.0 => /lib64/tls/libpthread.so.0 (0x00007fe4c7a5a000) /usr/bin/smbcontrol: libcap.so.1 => /lib64/libcap.so.1 (0x00007f6133e37000) libresolv.so.2 => /lib64/libresolv.so.2 (0x00007f6133d24000) libnsl.so.1 => /lib64/libnsl.so.1 (0x00007f6133c0e000) libdl.so.2 => /lib64/libdl.so.2 (0x00007f6133b0b000) librt.so.1 => /lib64/tls/librt.so.1 (0x00007f61339f1000) libldap-2.2.so.7 => /usr/lib64/libldap-2.2.so.7 (0x00007f61338bb000) liblber-2.2.so.7 => /usr/lib64/liblber-2.2.so.7 (0x00007f61337ac000) libpopt.so.0 => /usr/lib64/libpopt.so.0 (0x00007f61336a4000) libtalloc.so.1 => /usr/lib64/libtalloc.so.1 (0x00007f613359c000) libtdb.so.1 => /usr/lib64/libtdb.so.1 (0x00007f613348f000) libc.so.6 => /lib64/tls/libc.so.6 (0x00007f6133269000) /lib64/ld-linux-x86-64.so.2 (0x00007f6133f3b000) libpthread.so.0 => /lib64/tls/libpthread.so.0 (0x00007f6133155000) libsasl2.so.2 => /usr/lib64/libsasl2.so.2 (0x00007f613303e000) libssl.so.5 => /lib64/libssl.so.5 (0x00007f6132ef5000) libcrypto.so.5 => /lib64/libcrypto.so.5 (0x00007f6132c85000) libgssapi_krb5.so.2 => /usr/kerberos/lib64/libgssapi_krb5.so.2 (0x00007f6132b6d000) libkrb5.so.3 => /usr/kerberos/lib64/libkrb5.so.3 (0x00007f61329f3000) libcom_err.so.3 => /usr/kerberos/lib64/libcom_err.so.3 (0x00007f61328ef000) libk5crypto.so.3 => /usr/kerberos/lib64/libk5crypto.so.3 (0x00007f61327cb000) libz.so.1 => /usr/lib64/libz.so.1 (0x00007f61326b6000) libkrb5support.so.0 => /usr/kerberos/lib64/libkrb5support.so.0 (0x00007f61325b3000) /usr/bin/smbpasswd: libldap-2.2.so.7 => /usr/lib64/libldap-2.2.so.7 (0x00007f9eaea1f000) liblber-2.2.so.7 => /usr/lib64/liblber-2.2.so.7 (0x00007f9eae910000) libcap.so.1 => /lib64/libcap.so.1 (0x00007f9eae80c000) libresolv.so.2 => /lib64/libresolv.so.2 (0x00007f9eae6f9000) libnsl.so.1 => /lib64/libnsl.so.1 (0x00007f9eae5e3000) libdl.so.2 => /lib64/libdl.so.2 (0x00007f9eae4e0000) librt.so.1 => /lib64/tls/librt.so.1 (0x00007f9eae3c6000) libpopt.so.0 => /usr/lib64/libpopt.so.0 (0x00007f9eae2be000) libgssapi_krb5.so.2 => /usr/kerberos/lib64/libgssapi_krb5.so.2 (0x00007f9eae1a6000) libkrb5.so.3 => /usr/kerberos/lib64/libkrb5.so.3 (0x00007f9eae02c000) libk5crypto.so.3 => /usr/kerberos/lib64/libk5crypto.so.3 (0x00007f9eadf08000) libkrb5support.so.0 => /usr/kerberos/lib64/libkrb5support.so.0 (0x00007f9eade05000) libcom_err.so.3 => /usr/kerberos/lib64/libcom_err.so.3 (0x00007f9eadd01000) libtalloc.so.1 => /usr/lib64/libtalloc.so.1 (0x00007f9eadbf9000) libtdb.so.1 => /usr/lib64/libtdb.so.1 (0x00007f9eadaec000) libwbclient.so.0 => /usr/lib64/libwbclient.so.0 (0x00007f9ead9e0000) libz.so.1 => /usr/lib64/libz.so.1 (0x00007f9ead8cb000) libc.so.6 => /lib64/tls/libc.so.6 (0x00007f9ead6a5000) libsasl2.so.2 => /usr/lib64/libsasl2.so.2 (0x00007f9ead58e000) libssl.so.5 => /lib64/libssl.so.5 (0x00007f9ead445000) libcrypto.so.5 => /lib64/libcrypto.so.5 (0x00007f9ead1d5000) /lib64/ld-linux-x86-64.so.2 (0x00007f9eaeb55000) libpthread.so.0 => /lib64/tls/libpthread.so.0 (0x00007f9ead0c1000) /usr/bin/smbprint: not a dynamic executable /usr/bin/smbstatus: libcap.so.1 => /lib64/libcap.so.1 (0x00007ffc9b5d5000) libresolv.so.2 => /lib64/libresolv.so.2 (0x00007ffc9b4c2000) libnsl.so.1 => /lib64/libnsl.so.1 (0x00007ffc9b3ac000) libdl.so.2 => /lib64/libdl.so.2 (0x00007ffc9b2a9000) librt.so.1 => /lib64/tls/librt.so.1 (0x00007ffc9b18f000) libldap-2.2.so.7 => /usr/lib64/libldap-2.2.so.7 (0x00007ffc9b059000) liblber-2.2.so.7 => /usr/lib64/liblber-2.2.so.7 (0x00007ffc9af4a000) libpopt.so.0 => /usr/lib64/libpopt.so.0 (0x00007ffc9ae42000) libtalloc.so.1 => /usr/lib64/libtalloc.so.1 (0x00007ffc9ad3a000) libtdb.so.1 => /usr/lib64/libtdb.so.1 (0x00007ffc9ac2d000) libc.so.6 => /lib64/tls/libc.so.6 (0x00007ffc9aa07000) /lib64/ld-linux-x86-64.so.2 (0x00007ffc9b6d9000) libpthread.so.0 => /lib64/tls/libpthread.so.0 (0x00007ffc9a8f3000) libsasl2.so.2 => /usr/lib64/libsasl2.so.2 (0x00007ffc9a7dc000) libssl.so.5 => /lib64/libssl.so.5 (0x00007ffc9a693000) libcrypto.so.5 => /lib64/libcrypto.so.5 (0x00007ffc9a423000) libgssapi_krb5.so.2 => /usr/kerberos/lib64/libgssapi_krb5.so.2 (0x00007ffc9a30b000) libkrb5.so.3 => /usr/kerberos/lib64/libkrb5.so.3 (0x00007ffc9a191000) libcom_err.so.3 => /usr/kerberos/lib64/libcom_err.so.3 (0x00007ffc9a08d000) libk5crypto.so.3 => /usr/kerberos/lib64/libk5crypto.so.3 (0x00007ffc99f69000) libz.so.1 => /usr/lib64/libz.so.1 (0x00007ffc99e54000) libkrb5support.so.0 => /usr/kerberos/lib64/libkrb5support.so.0 (0x00007ffc99d51000) /usr/bin/smbtar: not a dynamic executable [root@proteo-replica ~]# ldd /usr/sbin/smbd /usr/bin/smb* | grep -r "lib64" libldap-2.2.so.7 => /usr/lib64/libldap-2.2.so.7 (0x00007fe322205000) liblber-2.2.so.7 => /usr/lib64/liblber-2.2.so.7 (0x00007fe3220f6000) libgssapi_krb5.so.2 => /usr/kerberos/lib64/libgssapi_krb5.so.2 (0x00007fe321fde000) libkrb5.so.3 => /usr/kerberos/lib64/libkrb5.so.3 (0x00007fe321e64000) libk5crypto.so.3 => /usr/kerberos/lib64/libk5crypto.so.3 (0x00007fe321d40000) libkrb5support.so.0 => /usr/kerberos/lib64/libkrb5support.so.0 (0x00007fe321c3d000) libcom_err.so.3 => /usr/kerberos/lib64/libcom_err.so.3 (0x00007fe321b39000) libresolv.so.2 => /lib64/libresolv.so.2 (0x00007fe321a26000) libcrypt.so.1 => /lib64/libcrypt.so.1 (0x00007fe3218f3000) libpam.so.0 => /lib64/libpam.so.0 (0x00007fe3217eb000) libacl.so.1 => /lib64/libacl.so.1 (0x00007fe3216e3000) libattr.so.1 => /lib64/libattr.so.1 (0x00007fe3215df000) libcap.so.1 => /lib64/libcap.so.1 (0x00007fe3214db000) libnsl.so.1 => /lib64/libnsl.so.1 (0x00007fe3213c5000) libdl.so.2 => /lib64/libdl.so.2 (0x00007fe3212c2000) librt.so.1 => /lib64/tls/librt.so.1 (0x00007fe3211a8000) libpopt.so.0 => /usr/lib64/libpopt.so.0 (0x00007fe3210a0000) libtalloc.so.1 => /usr/lib64/libtalloc.so.1 (0x00007fe320f98000) libtdb.so.1 => /usr/lib64/libtdb.so.1 (0x00007fe320e8b000) libwbclient.so.0 => /usr/lib64/libwbclient.so.0 (0x00007fe320d7f000) libz.so.1 => /usr/lib64/libz.so.1 (0x00007fe320c6a000) libc.so.6 => /lib64/tls/libc.so.6 (0x00007fe320a44000) libsasl2.so.2 => /usr/lib64/libsasl2.so.2 (0x00007fe32092d000) libssl.so.5 => /lib64/libssl.so.5 (0x00007fe3207e4000) libcrypto.so.5 => /lib64/libcrypto.so.5 (0x00007fe320574000) /lib64/ld-linux-x86-64.so.2 (0x00007fe32233b000) libpthread.so.0 => /lib64/tls/libpthread.so.0 (0x00007fe320460000) libcap.so.1 => /lib64/libcap.so.1 (0x00007fad1f282000) libresolv.so.2 => /lib64/libresolv.so.2 (0x00007fad1f16f000) libnsl.so.1 => /lib64/libnsl.so.1 (0x00007fad1f059000) libdl.so.2 => /lib64/libdl.so.2 (0x00007fad1ef56000) librt.so.1 => /lib64/tls/librt.so.1 (0x00007fad1ee3c000) libldap-2.2.so.7 => /usr/lib64/libldap-2.2.so.7 (0x00007fad1ed06000) liblber-2.2.so.7 => /usr/lib64/liblber-2.2.so.7 (0x00007fad1ebf7000) libpopt.so.0 => /usr/lib64/libpopt.so.0 (0x00007fad1eaef000) libtalloc.so.1 => /usr/lib64/libtalloc.so.1 (0x00007fad1e9e7000) libtdb.so.1 => /usr/lib64/libtdb.so.1 (0x00007fad1e8da000) libc.so.6 => /lib64/tls/libc.so.6 (0x00007fad1e6b4000) /lib64/ld-linux-x86-64.so.2 (0x00007fad1f386000) libpthread.so.0 => /lib64/tls/libpthread.so.0 (0x00007fad1e5a0000) libsasl2.so.2 => /usr/lib64/libsasl2.so.2 (0x00007fad1e489000) libssl.so.5 => /lib64/libssl.so.5 (0x00007fad1e340000) libcrypto.so.5 => /lib64/libcrypto.so.5 (0x00007fad1e0d0000) libgssapi_krb5.so.2 => /usr/kerberos/lib64/libgssapi_krb5.so.2 (0x00007fad1dfb8000) libkrb5.so.3 => /usr/kerberos/lib64/libkrb5.so.3 (0x00007fad1de3e000) libcom_err.so.3 => /usr/kerberos/lib64/libcom_err.so.3 (0x00007fad1dd3a000) libk5crypto.so.3 => /usr/kerberos/lib64/libk5crypto.so.3 (0x00007fad1dc16000) libz.so.1 => /usr/lib64/libz.so.1 (0x00007fad1db01000) libkrb5support.so.0 => /usr/kerberos/lib64/libkrb5support.so.0 (0x00007fad1d9fe000) libldap-2.2.so.7 => /usr/lib64/libldap-2.2.so.7 (0x00007f4551e92000) liblber-2.2.so.7 => /usr/lib64/liblber-2.2.so.7 (0x00007f4551d83000) libcap.so.1 => /lib64/libcap.so.1 (0x00007f4551c7f000) libresolv.so.2 => /lib64/libresolv.so.2 (0x00007f4551b6c000) libnsl.so.1 => /lib64/libnsl.so.1 (0x00007f4551a56000) libdl.so.2 => /lib64/libdl.so.2 (0x00007f4551953000) librt.so.1 => /lib64/tls/librt.so.1 (0x00007f4551839000) libpopt.so.0 => /usr/lib64/libpopt.so.0 (0x00007f4551731000) libgssapi_krb5.so.2 => /usr/kerberos/lib64/libgssapi_krb5.so.2 (0x00007f4551619000) libkrb5.so.3 => /usr/kerberos/lib64/libkrb5.so.3 (0x00007f455149f000) libk5crypto.so.3 => /usr/kerberos/lib64/libk5crypto.so.3 (0x00007f455137b000) libkrb5support.so.0 => /usr/kerberos/lib64/libkrb5support.so.0 (0x00007f4551278000) libcom_err.so.3 => /usr/kerberos/lib64/libcom_err.so.3 (0x00007f4551174000) libtalloc.so.1 => /usr/lib64/libtalloc.so.1 (0x00007f455106c000) libtdb.so.1 => /usr/lib64/libtdb.so.1 (0x00007f4550f5f000) libwbclient.so.0 => /usr/lib64/libwbclient.so.0 (0x00007f4550e53000) libz.so.1 => /usr/lib64/libz.so.1 (0x00007f4550d3e000) libc.so.6 => /lib64/tls/libc.so.6 (0x00007f4550b18000) libsasl2.so.2 => /usr/lib64/libsasl2.so.2 (0x00007f4550a01000) libssl.so.5 => /lib64/libssl.so.5 (0x00007f45508b8000) libcrypto.so.5 => /lib64/libcrypto.so.5 (0x00007f4550648000) /lib64/ld-linux-x86-64.so.2 (0x00007f4551fc8000) libpthread.so.0 => /lib64/tls/libpthread.so.0 (0x00007f4550534000) libcap.so.1 => /lib64/libcap.so.1 (0x00007f03c54c6000) libresolv.so.2 => /lib64/libresolv.so.2 (0x00007f03c53b3000) libnsl.so.1 => /lib64/libnsl.so.1 (0x00007f03c529d000) libdl.so.2 => /lib64/libdl.so.2 (0x00007f03c519a000) librt.so.1 => /lib64/tls/librt.so.1 (0x00007f03c5080000) libldap-2.2.so.7 => /usr/lib64/libldap-2.2.so.7 (0x00007f03c4f4a000) liblber-2.2.so.7 => /usr/lib64/liblber-2.2.so.7 (0x00007f03c4e3b000) libpopt.so.0 => /usr/lib64/libpopt.so.0 (0x00007f03c4d33000) libtalloc.so.1 => /usr/lib64/libtalloc.so.1 (0x00007f03c4c2b000) libtdb.so.1 => /usr/lib64/libtdb.so.1 (0x00007f03c4b1e000) libc.so.6 => /lib64/tls/libc.so.6 (0x00007f03c48f8000) /lib64/ld-linux-x86-64.so.2 (0x00007f03c55ca000) libpthread.so.0 => /lib64/tls/libpthread.so.0 (0x00007f03c47e4000) libsasl2.so.2 => /usr/lib64/libsasl2.so.2 (0x00007f03c46cd000) libssl.so.5 => /lib64/libssl.so.5 (0x00007f03c4584000) libcrypto.so.5 => /lib64/libcrypto.so.5 (0x00007f03c4314000) libgssapi_krb5.so.2 => /usr/kerberos/lib64/libgssapi_krb5.so.2 (0x00007f03c41fc000) libkrb5.so.3 => /usr/kerberos/lib64/libkrb5.so.3 (0x00007f03c4082000) libcom_err.so.3 => /usr/kerberos/lib64/libcom_err.so.3 (0x00007f03c3f7e000) libk5crypto.so.3 => /usr/kerberos/lib64/libk5crypto.so.3 (0x00007f03c3e5a000) libz.so.1 => /usr/lib64/libz.so.1 (0x00007f03c3d45000) libkrb5support.so.0 => /usr/kerberos/lib64/libkrb5support.so.0 (0x00007f03c3c42000) # ldd /usr/sbin/smbd /usr/bin/smb* | grep -v "lib64" /usr/sbin/smbd: /usr/bin/smbcontrol: /usr/bin/smbpasswd: /usr/bin/smbprint: not a dynamic executable /usr/bin/smbstatus: /usr/bin/smbtar: not a dynamic executable If there is no other binary in relation to Samba I didn't think about, I guess the Samba package is 64 bits. This should prevent me from any surprise. Best. Eric Sandeen wrote, On 31/08/14 04:46: > On 8/30/14, 2:33 PM, Samuel GRANJEAUD IR/INSERM wrote: >> Enabling the inode64 option has solved the problem. >> >> Final question: could some issues appear with SAMBA? > > ah, what sort of issues? > > Any application which uses i.e. a 32-bit stat() interface will return > -EOVERFLOW on a 64-bit inode. > > http://sandeen.net/wordpress/computers/the-world-wants-32-bit-inodes/ > http://blog.fmeh.org/2013/05/11/does-the-world-need-32-bit-inodes/ > > -Eric > Emmanuel Florac wrote, On 01/09/14 21:19: > Le Sat, 30 Aug 2014 21:33:46 +0200 vous écriviez: > >> Final question: could some issues appear with SAMBA? >> >> # smbstatus -V >> Version 3.4.5 > Is your whole distribution 64 bits, or only the kernel? However, I've > never had any problem with samba, but some with NFS. > _______________________________________________ xfs mailing list xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs ^ permalink raw reply [flat|nested] 10+ messages in thread
end of thread, other threads:[~2014-09-02 7:22 UTC | newest] Thread overview: 10+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2014-08-29 10:08 Run out of inodes? Samuel Granjeaud 2014-08-29 11:43 ` Emmanuel Florac 2014-08-29 11:48 ` Brian Foster 2014-08-29 13:29 ` Samuel Granjeaud 2014-08-29 15:02 ` Eric Sandeen 2014-08-29 15:22 ` Samuel Granjeaud 2014-08-30 19:33 ` Samuel GRANJEAUD IR/INSERM 2014-08-31 2:46 ` Eric Sandeen 2014-09-01 19:19 ` Emmanuel Florac 2014-09-02 7:22 ` Samuel Granjeaud
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox