limetech Posted March 9, 2022 Share Posted March 9, 2022 21 hours ago, JorgeB said: For rc2 it's 5.13.00, maybe despite xfs_growfs being part of xfsprogs the warning after the error comes from the kernel? Just a wild guess... Yes looking at the xfs kernel driver, the message is originating there. There is also some kind of "rate limit" on outputting the message, very odd. On 3/7/2022 at 5:31 AM, dalben said: This is what I got back from Gao Xiang. All over my head. What can I tell him? Let him know that we invoke xfs_growfs <mount-point> after each mount of an XFS file system. Further we guarantee the underlying size of the partition will either be unchanged or larger (never smaller). Under these conditions we expect the operation to expand the file system if the partition is now larger, or fail gracefully if not. This has been the "default" behavior for years. 2 Quote Link to comment
dalben Posted March 12, 2022 Author Share Posted March 12, 2022 Installed 6.10.0-RC3 and I still get the same error/warning Mar 12 09:50:42 tdm kernel: XFS (md1): Mounting V5 Filesystem Mar 12 09:50:42 tdm kernel: XFS (md1): Ending clean mount Mar 12 09:50:42 tdm kernel: xfs filesystem being mounted at /mnt/disk1 supports timestamps until 2038 (0x7fffffff) Mar 12 09:50:42 tdm emhttpd: shcmd (34): xfs_growfs /mnt/disk1 Mar 12 09:50:42 tdm kernel: XFS (md1): EXPERIMENTAL online shrink feature in use. Use at your own risk! Mar 12 09:50:42 tdm root: xfs_growfs: XFS_IOC_FSGROWFSDATA xfsctl failed: No space left on device Mar 12 09:50:42 tdm root: meta-data=/dev/md1 isize=512 agcount=32, agsize=137330687 blks Mar 12 09:50:42 tdm root: = sectsz=512 attr=2, projid32bit=1 Mar 12 09:50:42 tdm root: = crc=1 finobt=1, sparse=1, rmapbt=0 Mar 12 09:50:42 tdm root: = reflink=1 bigtime=0 inobtcount=0 Mar 12 09:50:42 tdm root: data = bsize=4096 blocks=4394581984, imaxpct=5 Mar 12 09:50:42 tdm root: = sunit=1 swidth=32 blks Mar 12 09:50:42 tdm root: naming =version 2 bsize=4096 ascii-ci=0, ftype=1 Mar 12 09:50:42 tdm root: log =internal log bsize=4096 blocks=521728, version=2 Mar 12 09:50:42 tdm root: = sectsz=512 sunit=1 blks, lazy-count=1 Mar 12 09:50:42 tdm root: realtime =none extsz=4096 blocks=0, rtextents=0 Mar 12 09:50:42 tdm emhttpd: shcmd (34): exit status: 1 Mar 12 09:50:42 tdm emhttpd: shcmd (35): mkdir -p /mnt/disk2 Mar 12 09:50:42 tdm emhttpd: shcmd (36): mount -t xfs -o noatime,nouuid /dev/md2 /mnt/disk2 Mar 12 09:50:42 tdm kernel: XFS (md2): Mounting V5 Filesystem Mar 12 09:50:42 tdm kernel: XFS (md2): Ending clean mount Mar 12 09:50:42 tdm emhttpd: shcmd (37): xfs_growfs /mnt/disk2 Mar 12 09:50:42 tdm kernel: xfs filesystem being mounted at /mnt/disk2 supports timestamps until 2038 (0x7fffffff) Mar 12 09:50:43 tdm root: xfs_growfs: XFS_IOC_FSGROWFSDATA xfsctl failed: No space left on device Mar 12 09:50:43 tdm root: meta-data=/dev/md2 isize=512 agcount=32, agsize=137330687 blks Mar 12 09:50:43 tdm root: = sectsz=512 attr=2, projid32bit=1 Mar 12 09:50:43 tdm root: = crc=1 finobt=1, sparse=1, rmapbt=0 Mar 12 09:50:43 tdm root: = reflink=1 bigtime=0 inobtcount=0 Mar 12 09:50:43 tdm root: data = bsize=4096 blocks=4394581984, imaxpct=5 Mar 12 09:50:43 tdm root: = sunit=1 swidth=32 blks Mar 12 09:50:43 tdm root: naming =version 2 bsize=4096 ascii-ci=0, ftype=1 Mar 12 09:50:43 tdm root: log =internal log bsize=4096 blocks=521728, version=2 Mar 12 09:50:43 tdm root: = sectsz=512 sunit=1 blks, lazy-count=1 Mar 12 09:50:43 tdm root: realtime =none extsz=4096 blocks=0, rtextents=0 Mar 12 09:50:43 tdm emhttpd: shcmd (37): exit status: 1 Mar 12 09:50:43 tdm emhttpd: shcmd (38): mkdir -p /mnt/disk3 Mar 12 09:50:43 tdm emhttpd: shcmd (39): mount -t xfs -o noatime,nouuid /dev/md3 /mnt/disk3 Mar 12 09:50:43 tdm kernel: XFS (md3): Mounting V5 Filesystem Mar 12 09:50:43 tdm kernel: XFS (md3): Ending clean mount Mar 12 09:50:43 tdm emhttpd: shcmd (40): xfs_growfs /mnt/disk3 Mar 12 09:50:43 tdm kernel: xfs filesystem being mounted at /mnt/disk3 supports timestamps until 2038 (0x7fffffff) Mar 12 09:50:43 tdm root: meta-data=/dev/md3 isize=512 agcount=32, agsize=30523583 blks Mar 12 09:50:43 tdm root: = sectsz=512 attr=2, projid32bit=1 Mar 12 09:50:43 tdm root: = crc=1 finobt=1, sparse=1, rmapbt=0 Mar 12 09:50:43 tdm root: = reflink=1 bigtime=0 inobtcount=0 Mar 12 09:50:43 tdm root: data = bsize=4096 blocks=976754633, imaxpct=5 Mar 12 09:50:43 tdm root: = sunit=1 swidth=32 blks Mar 12 09:50:43 tdm root: naming =version 2 bsize=4096 ascii-ci=0, ftype=1 Mar 12 09:50:43 tdm root: log =internal log bsize=4096 blocks=476930, version=2 Mar 12 09:50:43 tdm root: = sectsz=512 sunit=1 blks, lazy-count=1 Mar 12 09:50:43 tdm root: realtime =none extsz=4096 blocks=0, rtextents=0 Mar 12 09:50:43 tdm emhttpd: shcmd (41): mkdir -p /mnt/cache Quote Link to comment
JorgeB Posted March 14, 2022 Share Posted March 14, 2022 Did some tests with a 12TB disk and I think I found the issue, or at least what's causing it. Note that large disks formatted with v6.9.x or below don't have this issue after upgrading to v6.10, problem is with large disks formatted in the array with v6.10, looks like it's caused by the MD driver showing the disk as: Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 4096 bytes / 131072 bytes vs v6.9 Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes actual disk values Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes With v6.9.x and earlier the physical sector size also shows as 512 and there's no problem, but the I/O size is also 512 unlike v6.10, where I/O sizes seem wrong, and likely the reason for not getting errors with disks formatted with v6.9 on v6.10. Output of xfs_growfs, note the agcount and agsize differences, also sunit and swidth, not sure if those are relevant (also sector size when formatting without the MD driver but that's expected). Disk formatted using the MD driver in v6.9, output with v6.9 or v6.10: meta-data=/dev/md1 isize=512 agcount=11, agsize=268435455 blks = sectsz=512 attr=2, projid32bit=1 = crc=1 finobt=1, sparse=1, rmapbt=0 = reflink=1 data = bsize=4096 blocks=2929721331, imaxpct=5 = sunit=0 swidth=0 blks naming =version 2 bsize=4096 ascii-ci=0, ftype=1 log =internal log bsize=4096 blocks=521728, version=2 = sectsz=512 sunit=0 blks, lazy-count=1 realtime =none extsz=4096 blocks=0, rtextents=0 Disk formatted using the MD driver in v6.10: meta-data=/dev/md1 isize=512 agcount=32, agsize=91553791 blks = sectsz=512 attr=2, projid32bit=1 = crc=1 finobt=1, sparse=1, rmapbt=0 = reflink=1 bigtime=0 inobtcount=0 data = bsize=4096 blocks=2929721312, imaxpct=5 = sunit=1 swidth=32 blks naming =version 2 bsize=4096 ascii-ci=0, ftype=1 log =internal log bsize=4096 blocks=521728, version=2 = sectsz=512 sunit=1 blks, lazy-count=1 realtime =none extsz=4096 blocks=0, rtextents=0 xfs_growfs: XFS_IOC_FSGROWFSDATA xfsctl failed: No space left on device Disk formatted without the MD driver in v6.10: meta-data=/dev/sdb1 isize=512 agcount=11, agsize=268435455 blks = sectsz=4096 attr=2, projid32bit=1 = crc=1 finobt=1, sparse=1, rmapbt=0 = reflink=1 bigtime=0 inobtcount=0 data = bsize=4096 blocks=2929721331, imaxpct=5 = sunit=0 swidth=0 blks naming =version 2 bsize=4096 ascii-ci=0, ftype=1 log =internal log bsize=4096 blocks=521728, version=2 = sectsz=4096 sunit=1 blks, lazy-count=1 realtime =none extsz=4096 blocks=0, rtextents=0 Only disks formatted using the MD driver in v6.10 display the "xfs_growfs: XFS_IOC_FSGROWFSDATA xfsctl failed: No space left on device" error (and experimental warning) after running xfs_growfs, so this looks to me like an Unraid issue, XFS maintainers unlikely to investigate this if the problem only manifests itself after formatting the disk with the out of tree MD driver. 2 1 1 Quote Link to comment
limetech Posted March 14, 2022 Share Posted March 14, 2022 9 hours ago, JorgeB said: Did some tests with a 12TB disk and I think I found the issue, or at least what's causing it. Thank you, confirms a suspicion. In md/unraid I changed min I/O size from 512 to 4096 since all I/O is 4K aligned and min 4K anyway (the page size) - but evidently not 😆 Fix is in -rc4. Not sure if this will require reformatting those drives or not. Quote Link to comment
dalben Posted March 14, 2022 Author Share Posted March 14, 2022 49 minutes ago, limetech said: Not sure if this will require reformatting those drives or not. Who would know then? And would that person know if all large drives formatted with 6.10 need to be reformatted or just the one throwing the error? Quote Link to comment
WingmanNZ Posted March 15, 2022 Share Posted March 15, 2022 8 hours ago, dalben said: Who would know then? And would that person know if all large drives formatted with 6.10 need to be reformatted or just the one throwing the error? I would like to know this as well. I have one 10TB drive that shows this error upon every boot. I have been following this thread closely and look forward to RC4. Thank you @JorgeB for your investigations! Quote Link to comment
ChatNoir Posted March 15, 2022 Share Posted March 15, 2022 9 hours ago, dalben said: Who would know then? And would that person know if all large drives formatted with 6.10 need to be reformatted or just the one throwing the error? Maybe wait for rc4 to be available privately or publicly so the guys can make some tests and confirm ? Quote Link to comment
JorgeB Posted March 15, 2022 Share Posted March 15, 2022 14 hours ago, limetech said: Not sure if this will require reformatting those drives or not. I would expect so but will test once rc4 is available. 14 hours ago, limetech said: In md/unraid I changed min I/O size from 512 to 4096 since all I/O is 4K aligned This should be better for performance, no? Though maybe there wouldn't be much of a difference... If md used 512/4096 for I/O limits and 512/4096 or 4096/4096 for I/O hints maybe this wouldn't happen? As I understand it mkfs.xfs uses the I/O hints values to optimize the fs layout, so the md driver showing 4096/131072 for those could cause issues. Possibly best just go back to how it was but don't mind keeping the disk empty for a few days to test if you decide it's worth it. Quote Link to comment
dalben Posted March 20, 2022 Author Share Posted March 20, 2022 Not sure if it was addressed in RC4 and if so there was any expectation of the error going away, but it's still there Mar 21 06:40:06 tdm kernel: XFS (md1): Mounting V5 Filesystem Mar 21 06:40:06 tdm kernel: XFS (md1): Ending clean mount Mar 21 06:40:06 tdm emhttpd: shcmd (34): xfs_growfs /mnt/disk1 Mar 21 06:40:06 tdm kernel: xfs filesystem being mounted at /mnt/disk1 supports timestamps until 2038 (0x7fffffff) Mar 21 06:40:06 tdm root: xfs_growfs: XFS_IOC_FSGROWFSDATA xfsctl failed: No space left on device Mar 21 06:40:06 tdm root: meta-data=/dev/md1 isize=512 agcount=32, agsize=137330687 blks Mar 21 06:40:06 tdm root: = sectsz=512 attr=2, projid32bit=1 Mar 21 06:40:06 tdm root: = crc=1 finobt=1, sparse=1, rmapbt=0 Mar 21 06:40:06 tdm root: = reflink=1 bigtime=0 inobtcount=0 Mar 21 06:40:06 tdm root: data = bsize=4096 blocks=4394581984, imaxpct=5 Mar 21 06:40:06 tdm root: = sunit=1 swidth=32 blks Mar 21 06:40:06 tdm root: naming =version 2 bsize=4096 ascii-ci=0, ftype=1 Mar 21 06:40:06 tdm root: log =internal log bsize=4096 blocks=521728, version=2 Mar 21 06:40:06 tdm root: = sectsz=512 sunit=1 blks, lazy-count=1 Mar 21 06:40:06 tdm root: realtime =none extsz=4096 blocks=0, rtextents=0 Mar 21 06:40:06 tdm kernel: XFS (md1): EXPERIMENTAL online shrink feature in use. Use at your own risk! Mar 21 06:40:06 tdm emhttpd: shcmd (34): exit status: 1 Mar 21 06:40:06 tdm emhttpd: shcmd (35): mkdir -p /mnt/disk2 Mar 21 06:40:06 tdm emhttpd: shcmd (36): mount -t xfs -o noatime,nouuid /dev/md2 /mnt/disk2 Mar 21 06:40:06 tdm kernel: XFS (md2): Mounting V5 Filesystem Mar 21 06:40:07 tdm kernel: XFS (md2): Ending clean mount Mar 21 06:40:07 tdm kernel: xfs filesystem being mounted at /mnt/disk2 supports timestamps until 2038 (0x7fffffff) Mar 21 06:40:07 tdm emhttpd: shcmd (37): xfs_growfs /mnt/disk2 Mar 21 06:40:07 tdm root: xfs_growfs: XFS_IOC_FSGROWFSDATA xfsctl failed: No space left on device Mar 21 06:40:07 tdm root: meta-data=/dev/md2 isize=512 agcount=32, agsize=137330687 blks Mar 21 06:40:07 tdm root: = sectsz=512 attr=2, projid32bit=1 Mar 21 06:40:07 tdm root: = crc=1 finobt=1, sparse=1, rmapbt=0 Mar 21 06:40:07 tdm root: = reflink=1 bigtime=0 inobtcount=0 Mar 21 06:40:07 tdm root: data = bsize=4096 blocks=4394581984, imaxpct=5 Mar 21 06:40:07 tdm root: = sunit=1 swidth=32 blks Mar 21 06:40:07 tdm root: naming =version 2 bsize=4096 ascii-ci=0, ftype=1 Mar 21 06:40:07 tdm root: log =internal log bsize=4096 blocks=521728, version=2 Mar 21 06:40:07 tdm root: = sectsz=512 sunit=1 blks, lazy-count=1 Mar 21 06:40:07 tdm root: realtime =none extsz=4096 blocks=0, rtextents=0 Mar 21 06:40:07 tdm emhttpd: shcmd (37): exit status: 1 Mar 21 06:40:07 tdm emhttpd: shcmd (38): mkdir -p /mnt/disk3 Mar 21 06:40:07 tdm emhttpd: shcmd (39): mount -t xfs -o noatime,nouuid /dev/md3 /mnt/disk3 Mar 21 06:40:07 tdm kernel: XFS (md3): Mounting V5 Filesystem Mar 21 06:40:07 tdm kernel: XFS (md3): Ending clean mount Mar 21 06:40:07 tdm kernel: xfs filesystem being mounted at /mnt/disk3 supports timestamps until 2038 (0x7fffffff) Mar 21 06:40:07 tdm emhttpd: shcmd (40): xfs_growfs /mnt/disk3 Mar 21 06:40:07 tdm root: meta-data=/dev/md3 isize=512 agcount=32, agsize=30523583 blks Mar 21 06:40:07 tdm root: = sectsz=512 attr=2, projid32bit=1 Mar 21 06:40:07 tdm root: = crc=1 finobt=1, sparse=1, rmapbt=0 Mar 21 06:40:07 tdm root: = reflink=1 bigtime=0 inobtcount=0 Mar 21 06:40:07 tdm root: data = bsize=4096 blocks=976754633, imaxpct=5 Mar 21 06:40:07 tdm root: = sunit=1 swidth=32 blks Mar 21 06:40:07 tdm root: naming =version 2 bsize=4096 ascii-ci=0, ftype=1 Mar 21 06:40:07 tdm root: log =internal log bsize=4096 blocks=476930, version=2 Mar 21 06:40:07 tdm root: = sectsz=512 sunit=1 blks, lazy-count=1 Mar 21 06:40:07 tdm root: realtime =none extsz=4096 blocks=0, rtextents=0 Mar 21 06:40:07 tdm emhttpd: shcmd (41): mkdir -p /mnt/cache Quote Link to comment
WingmanNZ Posted March 20, 2022 Share Posted March 20, 2022 (edited) I am running 6.10-RC4 and still have five 10TB disks that all report xfs_growfs: XFS_IOC_FSGROWFSDATA xfsctl failed: No space left on device when I run xfs_growfs /mnt/diskX Is there some way to fix this or do I need to offload the data and reformat these? Edited March 20, 2022 by WingmanNZ add "code" blocks Quote Link to comment
ChatNoir Posted March 21, 2022 Share Posted March 21, 2022 JorgeB proposed to do some testing but he will not be available this week (CW12). Don't know if someone from Limetech has some validation planned. Quote Link to comment
klogg Posted March 21, 2022 Share Posted March 21, 2022 I can confirm the warning is still appearing in rc4 as well. I added and formatted a 10TB drive (/dev/md2) while running rc3. Updated to rc4, this is from my logs after a reboot this morning. Mar 21 08:22:22 Marvin emhttpd: Mounting disks... Mar 21 08:22:22 Marvin emhttpd: shcmd (30): /sbin/btrfs device scan Mar 21 08:22:23 Marvin root: Scanning for Btrfs filesystems Mar 21 08:22:23 Marvin emhttpd: shcmd (31): mkdir -p /mnt/disk1 Mar 21 08:22:23 Marvin emhttpd: shcmd (32): mount -t xfs -o noatime,nouuid /dev/md1 /mnt/disk1 Mar 21 08:22:23 Marvin kernel: SGI XFS with ACLs, security attributes, no debug enabled Mar 21 08:22:23 Marvin kernel: XFS (md1): Mounting V5 Filesystem Mar 21 08:22:23 Marvin kernel: XFS (md1): Ending clean mount Mar 21 08:22:23 Marvin kernel: xfs filesystem being mounted at /mnt/disk1 supports timestamps until 2038 (0x7fffffff) Mar 21 08:22:23 Marvin emhttpd: shcmd (33): xfs_growfs /mnt/disk1 Mar 21 08:22:23 Marvin root: meta-data=/dev/md1 isize=512 agcount=10, agsize=268435455 blks Mar 21 08:22:23 Marvin root: = sectsz=512 attr=2, projid32bit=1 Mar 21 08:22:23 Marvin root: = crc=1 finobt=1, sparse=1, rmapbt=0 Mar 21 08:22:23 Marvin root: = reflink=1 bigtime=0 inobtcount=0 Mar 21 08:22:23 Marvin root: data = bsize=4096 blocks=2441609203, imaxpct=5 Mar 21 08:22:23 Marvin root: = sunit=0 swidth=0 blks Mar 21 08:22:23 Marvin root: naming =version 2 bsize=4096 ascii-ci=0, ftype=1 Mar 21 08:22:23 Marvin root: log =internal log bsize=4096 blocks=521728, version=2 Mar 21 08:22:23 Marvin root: = sectsz=512 sunit=0 blks, lazy-count=1 Mar 21 08:22:23 Marvin root: realtime =none extsz=4096 blocks=0, rtextents=0 Mar 21 08:22:23 Marvin emhttpd: shcmd (34): mkdir -p /mnt/disk2 Mar 21 08:22:23 Marvin emhttpd: shcmd (35): mount -t xfs -o noatime,nouuid /dev/md2 /mnt/disk2 Mar 21 08:22:23 Marvin kernel: XFS (md2): Mounting V5 Filesystem Mar 21 08:22:24 Marvin kernel: XFS (md2): Ending clean mount Mar 21 08:22:24 Marvin kernel: xfs filesystem being mounted at /mnt/disk2 supports timestamps until 2038 (0x7fffffff) Mar 21 08:22:24 Marvin emhttpd: shcmd (36): xfs_growfs /mnt/disk2 Mar 21 08:22:24 Marvin kernel: XFS (md2): EXPERIMENTAL online shrink feature in use. Use at your own risk! Mar 21 08:22:24 Marvin root: xfs_growfs: XFS_IOC_FSGROWFSDATA xfsctl failed: No space left on device Mar 21 08:22:24 Marvin root: meta-data=/dev/md2 isize=512 agcount=32, agsize=76300287 blks Mar 21 08:22:24 Marvin root: = sectsz=512 attr=2, projid32bit=1 Mar 21 08:22:24 Marvin root: = crc=1 finobt=1, sparse=1, rmapbt=0 Mar 21 08:22:24 Marvin root: = reflink=1 bigtime=0 inobtcount=0 Mar 21 08:22:24 Marvin root: data = bsize=4096 blocks=2441609184, imaxpct=5 Mar 21 08:22:24 Marvin root: = sunit=1 swidth=32 blks Mar 21 08:22:24 Marvin root: naming =version 2 bsize=4096 ascii-ci=0, ftype=1 Mar 21 08:22:24 Marvin root: log =internal log bsize=4096 blocks=521728, version=2 Mar 21 08:22:24 Marvin root: = sectsz=512 sunit=1 blks, lazy-count=1 Mar 21 08:22:24 Marvin root: realtime =none extsz=4096 blocks=0, rtextents=0 Mar 21 08:22:24 Marvin emhttpd: shcmd (36): exit status: 1 Mar 21 08:22:24 Marvin emhttpd: shcmd (37): mkdir -p /mnt/disk3 Mar 21 08:22:24 Marvin emhttpd: shcmd (38): mount -t xfs -o noatime,nouuid /dev/md3 /mnt/disk3 Mar 21 08:22:24 Marvin kernel: XFS (md3): Mounting V5 Filesystem Mar 21 08:22:24 Marvin kernel: XFS (md3): Ending clean mount Mar 21 08:22:24 Marvin kernel: xfs filesystem being mounted at /mnt/disk3 supports timestamps until 2038 (0x7fffffff) Mar 21 08:22:24 Marvin emhttpd: shcmd (39): xfs_growfs /mnt/disk3 Mar 21 08:22:24 Marvin root: meta-data=/dev/md3 isize=512 agcount=8, agsize=268435455 blks Mar 21 08:22:24 Marvin root: = sectsz=512 attr=2, projid32bit=1 Mar 21 08:22:24 Marvin root: = crc=1 finobt=1, sparse=0, rmapbt=0 Mar 21 08:22:24 Marvin root: = reflink=0 bigtime=0 inobtcount=0 Mar 21 08:22:24 Marvin root: data = bsize=4096 blocks=1953506633, imaxpct=5 Mar 21 08:22:24 Marvin root: = sunit=0 swidth=0 blks Mar 21 08:22:24 Marvin root: naming =version 2 bsize=4096 ascii-ci=0, ftype=1 Mar 21 08:22:24 Marvin root: log =internal log bsize=4096 blocks=521728, version=2 Mar 21 08:22:24 Marvin root: = sectsz=512 sunit=0 blks, lazy-count=1 Mar 21 08:22:24 Marvin root: realtime =none extsz=4096 blocks=0, rtextents=0 Mar 21 08:22:24 Marvin emhttpd: shcmd (40): mkdir -p /mnt/disk4 Mar 21 08:22:24 Marvin emhttpd: shcmd (41): mount -t xfs -o noatime,nouuid /dev/md4 /mnt/disk4 Mar 21 08:22:24 Marvin kernel: XFS (md4): Mounting V5 Filesystem Mar 21 08:22:24 Marvin kernel: XFS (md4): Ending clean mount Mar 21 08:22:24 Marvin kernel: xfs filesystem being mounted at /mnt/disk4 supports timestamps until 2038 (0x7fffffff) Mar 21 08:22:24 Marvin emhttpd: shcmd (42): xfs_growfs /mnt/disk4 Mar 21 08:22:24 Marvin root: meta-data=/dev/md4 isize=512 agcount=6, agsize=268435455 blks Mar 21 08:22:24 Marvin root: = sectsz=512 attr=2, projid32bit=1 Mar 21 08:22:24 Marvin root: = crc=1 finobt=1, sparse=1, rmapbt=0 Mar 21 08:22:24 Marvin root: = reflink=0 bigtime=0 inobtcount=0 Mar 21 08:22:24 Marvin root: data = bsize=4096 blocks=1465130633, imaxpct=5 Mar 21 08:22:24 Marvin root: = sunit=0 swidth=0 blks Mar 21 08:22:24 Marvin root: naming =version 2 bsize=4096 ascii-ci=0, ftype=1 Mar 21 08:22:24 Marvin root: log =internal log bsize=4096 blocks=521728, version=2 Mar 21 08:22:24 Marvin root: = sectsz=512 sunit=0 blks, lazy-count=1 Mar 21 08:22:24 Marvin root: realtime =none extsz=4096 blocks=0, rtextents=0 I suspect that a reformat will be required, but I haven't tested that theory yet since it will require re-shuffling quite a lot of data to empty that drive. Quote Link to comment
JorgeB Posted March 21, 2022 Share Posted March 21, 2022 6 hours ago, klogg said: I can confirm the warning is still appearing in rc4 as well. Kind of expected that, it should be fixed for newly formatted disks (and will test that tomorrow to confirm) but warning will remain for disks formatted/rebuilt with rc1-rc3. Quote Link to comment
klogg Posted March 21, 2022 Share Posted March 21, 2022 2 hours ago, JorgeB said: Kind of expected that... Same, but it is good to have dreams. 🙂 Thanks for your help on this. Quote Link to comment
JorgeB Posted March 22, 2022 Share Posted March 22, 2022 12 hours ago, JorgeB said: it should be fixed for newly formatted disks It is fixed. 3 Quote Link to comment
WingmanNZ Posted March 22, 2022 Share Posted March 22, 2022 13 minutes ago, JorgeB said: It is fixed. Time to shuffle data around from five 10TB drives Quote Link to comment
dalben Posted March 22, 2022 Author Share Posted March 22, 2022 Thanks @JorgeB. Appreciate the troubleshooting and testing. 11 minutes ago, WingmanNZ said: Time to shuffle data around from five 10TB drives Yeah, but 18Gb drives for me. What fun Quote Link to comment
klogg Posted March 23, 2022 Share Posted March 23, 2022 Reformatted through UD this morning, rebooted, no more error. Thanks @JorgeB Mar 23 12:24:21 Marvin emhttpd: Mounting disks... Mar 23 12:24:21 Marvin emhttpd: shcmd (30): /sbin/btrfs device scan Mar 23 12:24:21 Marvin root: Scanning for Btrfs filesystems Mar 23 12:24:21 Marvin emhttpd: shcmd (31): mkdir -p /mnt/disk1 Mar 23 12:24:21 Marvin emhttpd: shcmd (32): mount -t xfs -o noatime,nouuid /dev/md1 /mnt/disk1 Mar 23 12:24:21 Marvin kernel: SGI XFS with ACLs, security attributes, no debug enabled Mar 23 12:24:21 Marvin kernel: XFS (md1): Mounting V5 Filesystem Mar 23 12:24:21 Marvin kernel: XFS (md1): Ending clean mount Mar 23 12:24:21 Marvin kernel: xfs filesystem being mounted at /mnt/disk1 supports timestamps until 2038 (0x7fffffff) Mar 23 12:24:21 Marvin emhttpd: shcmd (33): xfs_growfs /mnt/disk1 Mar 23 12:24:21 Marvin root: meta-data=/dev/md1 isize=512 agcount=10, agsize=268435455 blks Mar 23 12:24:21 Marvin root: = sectsz=512 attr=2, projid32bit=1 Mar 23 12:24:21 Marvin root: = crc=1 finobt=1, sparse=1, rmapbt=0 Mar 23 12:24:21 Marvin root: = reflink=1 bigtime=0 inobtcount=0 Mar 23 12:24:21 Marvin root: data = bsize=4096 blocks=2441609203, imaxpct=5 Mar 23 12:24:21 Marvin root: = sunit=0 swidth=0 blks Mar 23 12:24:21 Marvin root: naming =version 2 bsize=4096 ascii-ci=0, ftype=1 Mar 23 12:24:21 Marvin root: log =internal log bsize=4096 blocks=521728, version=2 Mar 23 12:24:21 Marvin root: = sectsz=512 sunit=0 blks, lazy-count=1 Mar 23 12:24:21 Marvin root: realtime =none extsz=4096 blocks=0, rtextents=0 Mar 23 12:24:21 Marvin emhttpd: shcmd (34): mkdir -p /mnt/disk2 Mar 23 12:24:21 Marvin emhttpd: shcmd (35): mount -t xfs -o noatime,nouuid /dev/md2 /mnt/disk2 Mar 23 12:24:21 Marvin kernel: XFS (md2): Mounting V5 Filesystem Mar 23 12:24:22 Marvin kernel: XFS (md2): Ending clean mount Mar 23 12:24:22 Marvin kernel: xfs filesystem being mounted at /mnt/disk2 supports timestamps until 2038 (0x7fffffff) Mar 23 12:24:22 Marvin emhttpd: shcmd (36): xfs_growfs /mnt/disk2 Mar 23 12:24:22 Marvin root: meta-data=/dev/md2 isize=512 agcount=10, agsize=268435455 blks Mar 23 12:24:22 Marvin root: = sectsz=4096 attr=2, projid32bit=1 Mar 23 12:24:22 Marvin root: = crc=1 finobt=1, sparse=1, rmapbt=0 Mar 23 12:24:22 Marvin root: = reflink=1 bigtime=0 inobtcount=0 Mar 23 12:24:22 Marvin root: data = bsize=4096 blocks=2441609203, imaxpct=5 Mar 23 12:24:22 Marvin root: = sunit=0 swidth=0 blks Mar 23 12:24:22 Marvin root: naming =version 2 bsize=4096 ascii-ci=0, ftype=1 Mar 23 12:24:22 Marvin root: log =internal log bsize=4096 blocks=521728, version=2 Mar 23 12:24:22 Marvin root: = sectsz=4096 sunit=1 blks, lazy-count=1 Mar 23 12:24:22 Marvin root: realtime =none extsz=4096 blocks=0, rtextents=0 Mar 23 12:24:22 Marvin emhttpd: shcmd (37): mkdir -p /mnt/disk3 Mar 23 12:24:22 Marvin emhttpd: shcmd (38): mount -t xfs -o noatime,nouuid /dev/md3 /mnt/disk3 Mar 23 12:24:22 Marvin kernel: XFS (md3): Mounting V5 Filesystem Mar 23 12:24:22 Marvin kernel: XFS (md3): Ending clean mount Mar 23 12:24:22 Marvin kernel: xfs filesystem being mounted at /mnt/disk3 supports timestamps until 2038 (0x7fffffff) Mar 23 12:24:22 Marvin emhttpd: shcmd (39): xfs_growfs /mnt/disk3 Mar 23 12:24:22 Marvin root: meta-data=/dev/md3 isize=512 agcount=8, agsize=268435455 blks Mar 23 12:24:22 Marvin root: = sectsz=512 attr=2, projid32bit=1 Mar 23 12:24:22 Marvin root: = crc=1 finobt=1, sparse=0, rmapbt=0 Mar 23 12:24:22 Marvin root: = reflink=0 bigtime=0 inobtcount=0 Mar 23 12:24:22 Marvin root: data = bsize=4096 blocks=1953506633, imaxpct=5 Mar 23 12:24:22 Marvin root: = sunit=0 swidth=0 blks Mar 23 12:24:22 Marvin root: naming =version 2 bsize=4096 ascii-ci=0, ftype=1 Mar 23 12:24:22 Marvin root: log =internal log bsize=4096 blocks=521728, version=2 Mar 23 12:24:22 Marvin root: = sectsz=512 sunit=0 blks, lazy-count=1 Mar 23 12:24:22 Marvin root: realtime =none extsz=4096 blocks=0, rtextents=0 Mar 23 12:24:22 Marvin emhttpd: shcmd (40): mkdir -p /mnt/disk4 Mar 23 12:24:22 Marvin emhttpd: shcmd (41): mount -t xfs -o noatime,nouuid /dev/md4 /mnt/disk4 Mar 23 12:24:22 Marvin kernel: XFS (md4): Mounting V5 Filesystem Mar 23 12:24:22 Marvin kernel: XFS (md4): Ending clean mount Mar 23 12:24:22 Marvin kernel: xfs filesystem being mounted at /mnt/disk4 supports timestamps until 2038 (0x7fffffff) Mar 23 12:24:22 Marvin emhttpd: shcmd (42): xfs_growfs /mnt/disk4 Mar 23 12:24:22 Marvin root: meta-data=/dev/md4 isize=512 agcount=6, agsize=268435455 blks Mar 23 12:24:22 Marvin root: = sectsz=512 attr=2, projid32bit=1 Mar 23 12:24:22 Marvin root: = crc=1 finobt=1, sparse=1, rmapbt=0 Mar 23 12:24:22 Marvin root: = reflink=0 bigtime=0 inobtcount=0 Mar 23 12:24:22 Marvin root: data = bsize=4096 blocks=1465130633, imaxpct=5 Mar 23 12:24:22 Marvin root: = sunit=0 swidth=0 blks Mar 23 12:24:22 Marvin root: naming =version 2 bsize=4096 ascii-ci=0, ftype=1 Mar 23 12:24:22 Marvin root: log =internal log bsize=4096 blocks=521728, version=2 Mar 23 12:24:22 Marvin root: = sectsz=512 sunit=0 blks, lazy-count=1 Mar 23 12:24:22 Marvin root: realtime =none extsz=4096 blocks=0, rtextents=0 Mar 23 12:24:22 Marvin emhttpd: shcmd (43): mkdir -p /mnt/cache Quote Link to comment
dalben Posted March 27, 2022 Author Share Posted March 27, 2022 @JorgeB All reformatted and finished playing shuffle files. No more errors. Thanks 1 Quote Link to comment
tamito Posted May 27, 2022 Share Posted May 27, 2022 (edited) @JorgeB I have the same problem. So the procedure is to 1. stop array. 2. Take down the failure drive. 3. Format the drive. 4. Add drive back to array and rebuild the parity Am I correct? Edited May 27, 2022 by tamito Quote Link to comment
JorgeB Posted May 27, 2022 Share Posted May 27, 2022 2 minutes ago, tamito said: Am I correct? Nope, no need to disable the drive and formatting will deleted everything, it can't be rebuilt from parity, procedure is: -move all data from that drive to another place -format it -restore the data Quote Link to comment
tamito Posted May 27, 2022 Share Posted May 27, 2022 Which command do I need to run for formatting if I don't need to stop array? Quote Link to comment
itimpi Posted May 27, 2022 Share Posted May 27, 2022 8 minutes ago, tamito said: Which command do I need to run for formatting if I don't need to stop array? The procedure is covered here in the online documentations accessible via the ‘Manual’ link at the bottom of the GUI. Quote Link to comment
JorgeB Posted May 27, 2022 Share Posted May 27, 2022 7 minutes ago, tamito said: if I don't need to stop array? I didn't say you don't need to stop the array, you don't need to disable and rebuild the disk, was going to post the instructions but itimpi already did. 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.