# Longhorn showing disk as 0 bytes

**URL:** <https://forums.suse.com/t/longhorn-showing-disk-as-0-bytes/44072>\
**Category:** SUSE Storage\
**Created:** [September 17, 2024, 4:01pm UTC](https://forums.suse.com/t/longhorn-showing-disk-as-0-bytes/44072 "2024-09-17T16:01:22Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Mark\_Weaver](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/mark_weaver/32/11500_2.png) [@Mark\_Weaver](https://forums.suse.com/u/Mark_Weaver)\
**Post date:** [September 17, 2024, 4:01pm UTC](https://forums.suse.com/t/longhorn-showing-disk-as-0-bytes/44072/1 "2024-09-17T16:01:22Z")

</div>

![image](https://us1.discourse-cdn.com/flex022/uploads/suse/original/2X/9/91d1aa31938767762f31b64ddce9204a022895bd.png)

I’ve added nodes 4,5,6 and one of them shows the correct disk size but the others show zero bytes. I’m not sure how to proceed with diagnosing this and would like some advice.

I do get this:  
time=“2024-09-17T15:19:23Z” level=warning msg=“Failed to get filesystem device type of /var/lib/longhorn/” func=“controller.(\*ClusterInfo).collectNodeDiskCount” file=“setting\_controller.go:1936” controller=longhorn-setting error=“lstat /sys/class/block/vg1-longhorn: no such file or directory” node=eu4

which looks like a bug in about the right code area (/dev/mapper/vg1-longhorn is a symlink to /dev/dm-2 and /sys/class/block/dm-2 exists, i.e. longhorn should be following the symlink), but all the other nodes show the same warning

I can’t see any difference between the volumes (they are all lvs formatted as xfs, same size, same vg1 name/path, same fstab line), same permissions and same files (engine-binaries, longhorn-disk.cfg, etc)

Thanks,

Mark

---

<div class="post-metadata">

**Author:** ![Mark\_Weaver](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/mark_weaver/32/11500_2.png) [@Mark\_Weaver](https://forums.suse.com/u/Mark_Weaver)\
**Post date:** [September 18, 2024, 7:31pm UTC](https://forums.suse.com/t/longhorn-showing-disk-as-0-bytes/44072/2 "2024-09-18T19:31:30Z")

</div>

I have figured this out eventually – the problem was in fact “record diskUUID doesn’t match the one on the disk” showing the tooltip. It was fixed by deleting the default disk (which it’s not _obvious_ you can do, there is a little trash icon there), then creating a new one.