coreylane Posted December 14, 2021 Share Posted December 14, 2021 (edited) Is this normal behavior? Diagnostics attached.... root@darktower:~# grep XFS_IOC_FSGROWFSDATA /var/log/syslog Dec 14 01:11:32 darktower root: xfs_growfs: XFS_IOC_FSGROWFSDATA xfsctl failed: No space left on device Dec 14 01:11:33 darktower root: xfs_growfs: XFS_IOC_FSGROWFSDATA xfsctl failed: No space left on device Dec 14 01:11:33 darktower root: xfs_growfs: XFS_IOC_FSGROWFSDATA xfsctl failed: No space left on device Dec 14 01:11:34 darktower root: xfs_growfs: XFS_IOC_FSGROWFSDATA xfsctl failed: No space left on device darktower-diagnostics-20211214-0142.zip Edited December 14, 2021 by ceddybu Quote Link to comment
JorgeB Posted December 14, 2021 Share Posted December 14, 2021 Dec 14 01:11:32 darktower kernel: XFS (md1): EXPERIMENTAL online shrink feature in use. Use at your own risk! Don't know what this is about, first time I see it, try running a file system check. Quote Link to comment
coreylane Posted December 14, 2021 Author Share Posted December 14, 2021 I ran "xfs_repair -v" on md1 (and all other array disks) but these messages are still appearing in the logs. Is this the right command? "fsck.xfs" command just redirects me to manpage for "xfs_repair" root@darktower:~# grep EXPERIMENTAL /var/log/syslog Dec 14 16:22:28 darktower kernel: XFS (md1): EXPERIMENTAL online shrink feature in use. Use at your own risk! root@darktower:~# grep fail /var/log/syslog Dec 14 16:22:28 darktower root: xfs_growfs: XFS_IOC_FSGROWFSDATA xfsctl failed: No space left on device Dec 14 16:22:29 darktower root: xfs_growfs: XFS_IOC_FSGROWFSDATA xfsctl failed: No space left on device Dec 14 16:22:29 darktower root: xfs_growfs: XFS_IOC_FSGROWFSDATA xfsctl failed: No space left on device Dec 14 16:22:29 darktower root: xfs_growfs: XFS_IOC_FSGROWFSDATA xfsctl failed: No space left on device Quote Link to comment
JorgeB Posted December 15, 2021 Share Posted December 15, 2021 9 hours ago, ceddybu said: Is this the right command? Yes, note sure what happened to disk1, you'd need to backup and re-format or ask for help e.g. on the xfs mailing list. Quote Link to comment
reapola Posted January 19, 2022 Share Posted January 19, 2022 (edited) Did you get this fixed? Noticed the same in my log. Disk1 is a 12TB drive, the others are 8TB and disk1 was a new install/upgrade in November so it was a fresh format and parity rebuild. Jan 18 23:42:31 Zeus emhttpd: shcmd (37): mkdir -p /mnt/disk1 Jan 18 23:42:31 Zeus emhttpd: shcmd (38): mount -t xfs -o noatime /dev/md1 /mnt/disk1 Jan 18 23:42:31 Zeus kernel: SGI XFS with ACLs, security attributes, no debug enabled Jan 18 23:42:31 Zeus kernel: XFS (md1): Mounting V5 Filesystem Jan 18 23:42:31 Zeus kernel: XFS (md1): Ending clean mount Jan 18 23:42:32 Zeus kernel: xfs filesystem being mounted at /mnt/disk1 supports timestamps until 2038 (0x7fffffff) Jan 18 23:42:32 Zeus emhttpd: shcmd (39): xfs_growfs /mnt/disk1 Jan 18 23:42:32 Zeus kernel: XFS (md1): EXPERIMENTAL online shrink feature in use. Use at your own risk! Jan 18 23:42:32 Zeus root: xfs_growfs: XFS_IOC_FSGROWFSDATA xfsctl failed: No space left on device Jan 18 23:42:32 Zeus root: meta-data=/dev/md1 isize=512 agcount=32, agsize=91553791 blks Jan 18 23:42:32 Zeus root: = sectsz=512 attr=2, projid32bit=1 Jan 18 23:42:32 Zeus root: = crc=1 finobt=1, sparse=1, rmapbt=0 Jan 18 23:42:32 Zeus root: = reflink=1 bigtime=0 inobtcount=0 Jan 18 23:42:32 Zeus root: data = bsize=4096 blocks=2929721312, imaxpct=5 Jan 18 23:42:32 Zeus root: = sunit=1 swidth=32 blks Jan 18 23:42:32 Zeus root: naming =version 2 bsize=4096 ascii-ci=0, ftype=1 Jan 18 23:42:32 Zeus root: log =internal log bsize=4096 blocks=521728, version=2 Jan 18 23:42:32 Zeus root: = sectsz=512 sunit=1 blks, lazy-count=1 Jan 18 23:42:32 Zeus root: realtime =none extsz=4096 blocks=0, rtextents=0 Jan 18 23:42:32 Zeus emhttpd: shcmd (39): exit status: 1 Jan 18 23:42:32 Zeus emhttpd: shcmd (40): mkdir -p /mnt/disk2 Jan 18 23:42:32 Zeus emhttpd: shcmd (41): mount -t xfs -o noatime /dev/md2 /mnt/disk2 Jan 18 23:42:32 Zeus kernel: XFS (md2): Mounting V5 Filesystem Jan 18 23:42:32 Zeus kernel: XFS (md2): Ending clean mount Jan 18 23:42:32 Zeus kernel: xfs filesystem being mounted at /mnt/disk2 supports timestamps until 2038 (0x7fffffff) Jan 18 23:42:32 Zeus emhttpd: shcmd (42): xfs_growfs /mnt/disk2 Jan 18 23:42:32 Zeus root: meta-data=/dev/md2 isize=512 agcount=8, agsize=244188659 blks Jan 18 23:42:32 Zeus root: = sectsz=512 attr=2, projid32bit=1 Jan 18 23:42:32 Zeus root: = crc=1 finobt=1, sparse=0, rmapbt=0 Jan 18 23:42:32 Zeus root: = reflink=0 bigtime=0 inobtcount=0 Jan 18 23:42:32 Zeus root: data = bsize=4096 blocks=1953506633, imaxpct=5 Jan 18 23:42:32 Zeus root: = sunit=0 swidth=0 blks Jan 18 23:42:32 Zeus root: naming =version 2 bsize=4096 ascii-ci=0, ftype=1 Jan 18 23:42:32 Zeus root: log =internal log bsize=4096 blocks=476930, version=2 Jan 18 23:42:32 Zeus root: = sectsz=512 sunit=0 blks, lazy-count=1 Jan 18 23:42:32 Zeus root: realtime =none extsz=4096 blocks=0, rtextents=0 Jan 18 23:42:32 Zeus emhttpd: shcmd (43): mkdir -p /mnt/disk3 Jan 18 23:42:32 Zeus emhttpd: shcmd (44): mount -t xfs -o noatime /dev/md3 /mnt/disk3 Jan 18 23:42:32 Zeus kernel: XFS (md3): Mounting V5 Filesystem Jan 18 23:42:32 Zeus kernel: XFS (md3): Ending clean mount Jan 18 23:42:32 Zeus kernel: xfs filesystem being mounted at /mnt/disk3 supports timestamps until 2038 (0x7fffffff) Jan 18 23:42:32 Zeus emhttpd: shcmd (45): xfs_growfs /mnt/disk3 Jan 18 23:42:32 Zeus root: meta-data=/dev/md3 isize=512 agcount=8, agsize=244188659 blks Jan 18 23:42:32 Zeus root: = sectsz=512 attr=2, projid32bit=1 Jan 18 23:42:32 Zeus root: = crc=1 finobt=1, sparse=0, rmapbt=0 Jan 18 23:42:32 Zeus root: = reflink=0 bigtime=0 inobtcount=0 Jan 18 23:42:32 Zeus root: data = bsize=4096 blocks=1953506633, imaxpct=5 Jan 18 23:42:32 Zeus root: = sunit=0 swidth=0 blks Jan 18 23:42:32 Zeus root: naming =version 2 bsize=4096 ascii-ci=0, ftype=1 Jan 18 23:42:32 Zeus root: log =internal log bsize=4096 blocks=476930, version=2 Jan 18 23:42:32 Zeus root: = sectsz=512 sunit=0 blks, lazy-count=1 Jan 18 23:42:32 Zeus root: realtime =none extsz=4096 blocks=0, rtextents=0 Edited January 19, 2022 by reapola Quote Link to comment
rxn123talon Posted February 7, 2022 Share Posted February 7, 2022 Did either of you figure out what this is? I just noticed that my server is giving me the same messages. One in syslog of xfs_growfs: XFS_IOC_FSGROWFSDATA xfsctl failed and the same "online shrink feature in use". Were you able to resolve this and if so, how? Quote Link to comment
manHands Posted February 7, 2022 Share Posted February 7, 2022 14 minutes ago, rxn123talon said: Did either of you figure out what this is? I just noticed that my server is giving me the same messages. One in syslog of xfs_growfs: XFS_IOC_FSGROWFSDATA xfsctl failed and the same "online shrink feature in use". Were you able to resolve this and if so, how? I had the same issue. I moved all the data off the drive in question, removed from array, re-formatted, and then added back to the array. All good now. Quote Link to comment
reapola Posted February 7, 2022 Share Posted February 7, 2022 (edited) 2 hours ago, rxn123talon said: Did either of you figure out what this is? I just noticed that my server is giving me the same messages. One in syslog of xfs_growfs: XFS_IOC_FSGROWFSDATA xfsctl failed and the same "online shrink feature in use". Were you able to resolve this and if so, how? No, still an issue but only complains at boot. @manHandsgood that it worked for you but I'd rather not start moving data about. @limetech , any ideas? Edited February 7, 2022 by reapola Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.