Resized Partition Mount Point Not Understood

English Install/Boot/Login
1

Running LEAP 42.1 with Plasma desktop I have a hardware RAID and have created 5 partitions, sda1 for EFI boot, sda2 swap, sda3 / sda4 /home and sda5 /data.
When I created the sda5 /data partition I only used half of the available space. The /data partition (formatted XFS) is used for multimedia. I have found that I now need to resize the partition to use all of the available space.

I unmounted the partition and using yast partitioner tried to resize to “maximum”. I received an error message about overlapping something (sorry, lost the message) so I reduced the size from 4.91 TiB to 4.90 TiB and went ahead with the resize. No error messages this time but a warning that it could take some time.

Now all appears well but in the expert partitioner sda5 is shown at:-

/tmp/libstorage-iztF91/tmp-xfs-mp

with no sign of /data.

Using Dolphin however the soft link to the partition in my home directory is still working and all the multimedia files are in place.

Is this a feature of some process which is continuing in the background and will eventually be completed?
Budgie2

2

Did you remount it? The resize may have changed the UUID and it may look like a new partition not the old

3

Please show

fdisk -l

cat /etc/fstab

mount | grep '^/dev'

ls -l /dev/disk/by*

to provide some information.

4

Hi, thanks for the reply. No I did not remount it, it seems to have done that itself. All files present and accessible using dolphin but no sign of the original mount name “/data”
Your UUID point seems likely. I have some work to do and will post what I find.

5

Hi Henk:

ibmserver2:~ # fdisk -l

Disk /dev/sda: 5.5 TiB, 5993995960320 bytes, 11707023360 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: F2939456-093E-4312-9091-673EDA79A76E

Device          Start         End     Sectors  Size Type
/dev/sda1        2048      321535      319488  156M EFI System
/dev/sda2      321536     4530175     4208640    2G Microsoft basic data
/dev/sda3     4530176    88422399    83892224   40G Microsoft basic data
/dev/sda4    88422400  1162158079  1073735680  512G Microsoft basic data
/dev/sda5  1162158080 11684829469 10522671390  4.9T Microsoft basic data

ibmserver2:~ #

and:

ibmserver2:~ # cat /etc/fstab
UUID=46f191b6-7472-49c0-bd98-75824020d947       swap    swap    defaults 0 0 
UUID=a5a2612d-d0cb-4b05-a3cf-cc95ecd0235b       /       btrfs   defaults 0 0 
UUID=a5a2612d-d0cb-4b05-a3cf-cc95ecd0235b       /boot/grub2/i386-pc     btrfs   subvol=boot/grub2/i386-pc 0 0 
UUID=a5a2612d-d0cb-4b05-a3cf-cc95ecd0235b       /boot/grub2/x86_64-efi  btrfs   subvol=boot/grub2/x86_64-efi 0 0 
UUID=a5a2612d-d0cb-4b05-a3cf-cc95ecd0235b       /opt    btrfs   subvol=opt 0 0 
UUID=a5a2612d-d0cb-4b05-a3cf-cc95ecd0235b       /srv    btrfs   subvol=srv 0 0 
UUID=a5a2612d-d0cb-4b05-a3cf-cc95ecd0235b       /tmp    btrfs   subvol=tmp 0 0 
UUID=a5a2612d-d0cb-4b05-a3cf-cc95ecd0235b       /usr/local      btrfs   subvol=usr/local 0 0 
UUID=a5a2612d-d0cb-4b05-a3cf-cc95ecd0235b       /var/crash      btrfs   subvol=var/crash 0 0 
UUID=a5a2612d-d0cb-4b05-a3cf-cc95ecd0235b       /var/lib/mailman        btrfs   subvol=var/lib/mailman 0 0 
UUID=a5a2612d-d0cb-4b05-a3cf-cc95ecd0235b       /var/lib/named  btrfs   subvol=var/lib/named 0 0 
UUID=a5a2612d-d0cb-4b05-a3cf-cc95ecd0235b       /var/lib/pgsql  btrfs   subvol=var/lib/pgsql 0 0 
UUID=a5a2612d-d0cb-4b05-a3cf-cc95ecd0235b       /var/log        btrfs   subvol=var/log 0 0 
UUID=a5a2612d-d0cb-4b05-a3cf-cc95ecd0235b       /var/opt        btrfs   subvol=var/opt 0 0 
UUID=a5a2612d-d0cb-4b05-a3cf-cc95ecd0235b       /var/spool      btrfs   subvol=var/spool 0 0 
UUID=a5a2612d-d0cb-4b05-a3cf-cc95ecd0235b       /var/tmp        btrfs   subvol=var/tmp 0 0 
UUID=B738-D576  /boot/efi       vfat    umask=0002,utf8=true 0 0                                                                        
UUID=4ceac2e7-6bdc-40d2-9dff-da7a2099bf45       /home   xfs     defaults 1 2                                                            
UUID=a5a2612d-d0cb-4b05-a3cf-cc95ecd0235b       /.snapshots     btrfs   subvol=.snapshots 0 0                                           
UUID=4272b75a-ea72-4068-8826-e2dfc5611fd5       /data   xfs     defaults 1 2                                                            
192.168.169.132:/data/multimedia        /home/alastair/Temp_NFS nfs     defaults 0 0 
ibmserver2:~ #

and:-

ibmserver2:~ # mount | grep '^/dev'
/dev/sda3 on / type btrfs (rw,relatime,space_cache,subvolid=5,subvol=/)
/dev/sda3 on /.snapshots type btrfs (rw,relatime,space_cache,subvolid=275,subvol=/.snapshots)
/dev/sda3 on /var/tmp type btrfs (rw,relatime,space_cache,subvolid=270,subvol=/var/tmp)
/dev/sda3 on /var/spool type btrfs (rw,relatime,space_cache,subvolid=269,subvol=/var/spool)
/dev/sda3 on /var/opt type btrfs (rw,relatime,space_cache,subvolid=268,subvol=/var/opt)
/dev/sda3 on /var/log type btrfs (rw,relatime,space_cache,subvolid=267,subvol=/var/log)
/dev/sda3 on /var/lib/pgsql type btrfs (rw,relatime,space_cache,subvolid=266,subvol=/var/lib/pgsql)
/dev/sda3 on /var/lib/named type btrfs (rw,relatime,space_cache,subvolid=265,subvol=/var/lib/named)
/dev/sda3 on /var/lib/mailman type btrfs (rw,relatime,space_cache,subvolid=264,subvol=/var/lib/mailman)
/dev/sda3 on /var/crash type btrfs (rw,relatime,space_cache,subvolid=263,subvol=/var/crash)
/dev/sda3 on /usr/local type btrfs (rw,relatime,space_cache,subvolid=262,subvol=/usr/local)
/dev/sda3 on /tmp type btrfs (rw,relatime,space_cache,subvolid=261,subvol=/tmp)
/dev/sda3 on /srv type btrfs (rw,relatime,space_cache,subvolid=260,subvol=/srv)
/dev/sda3 on /opt type btrfs (rw,relatime,space_cache,subvolid=259,subvol=/opt)
/dev/sda3 on /boot/grub2/x86_64-efi type btrfs (rw,relatime,space_cache,subvolid=258,subvol=/boot/grub2/x86_64-efi)
/dev/sda3 on /boot/grub2/i386-pc type btrfs (rw,relatime,space_cache,subvolid=257,subvol=/boot/grub2/i386-pc)
/dev/sda1 on /boot/efi type vfat (rw,relatime,fmask=0002,dmask=0002,allow_utime=0020,codepage=437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/sda4 on /home type xfs (rw,relatime,attr2,inode64,noquota)
/dev/sda5 on /tmp/libstorage-iztF91/tmp-xfs-mp type xfs (rw,relatime,attr2,inode64,noquota)
/dev/sda5 on /data type xfs (rw,relatime,attr2,inode64,noquota)
ibmserver2:~ #

and:-

ibmserver2:~ # ls -l /dev/disk/by*
/dev/disk/by-id:
total 0
lrwxrwxrwx 1 root root  9 Feb 14 14:42 ata-IBM_SATA_DEVICE_81Y3681_M86E1KM4319 -> ../../sr0
lrwxrwxrwx 1 root root  9 Feb 21 14:57 scsi-3600605b0057337c01df4874d2e7f5d6e -> ../../sda
lrwxrwxrwx 1 root root 10 Feb 21 08:58 scsi-3600605b0057337c01df4874d2e7f5d6e-part1 -> ../../sda1
lrwxrwxrwx 1 root root 10 Feb 21 08:58 scsi-3600605b0057337c01df4874d2e7f5d6e-part2 -> ../../sda2
lrwxrwxrwx 1 root root 10 Feb 21 08:58 scsi-3600605b0057337c01df4874d2e7f5d6e-part3 -> ../../sda3
lrwxrwxrwx 1 root root 10 Feb 21 08:58 scsi-3600605b0057337c01df4874d2e7f5d6e-part4 -> ../../sda4
lrwxrwxrwx 1 root root 10 Feb 21 08:58 scsi-3600605b0057337c01df4874d2e7f5d6e-part5 -> ../../sda5
lrwxrwxrwx 1 root root  9 Feb 21 14:57 scsi-SIBM_ServeRAID_M5014_006e5d7f2e4d87f41dc0377305b00506 -> ../../sda
lrwxrwxrwx 1 root root 10 Feb 21 08:58 scsi-SIBM_ServeRAID_M5014_006e5d7f2e4d87f41dc0377305b00506-part1 -> ../../sda1
lrwxrwxrwx 1 root root 10 Feb 21 08:58 scsi-SIBM_ServeRAID_M5014_006e5d7f2e4d87f41dc0377305b00506-part2 -> ../../sda2
lrwxrwxrwx 1 root root 10 Feb 21 08:58 scsi-SIBM_ServeRAID_M5014_006e5d7f2e4d87f41dc0377305b00506-part3 -> ../../sda3
lrwxrwxrwx 1 root root 10 Feb 21 08:58 scsi-SIBM_ServeRAID_M5014_006e5d7f2e4d87f41dc0377305b00506-part4 -> ../../sda4
lrwxrwxrwx 1 root root 10 Feb 21 08:58 scsi-SIBM_ServeRAID_M5014_006e5d7f2e4d87f41dc0377305b00506-part5 -> ../../sda5
lrwxrwxrwx 1 root root  9 Feb 14 14:42 wwn-0x5001480000000000 -> ../../sr0
lrwxrwxrwx 1 root root  9 Feb 21 14:57 wwn-0x600605b0057337c01df4874d2e7f5d6e -> ../../sda
lrwxrwxrwx 1 root root 10 Feb 21 08:58 wwn-0x600605b0057337c01df4874d2e7f5d6e-part1 -> ../../sda1
lrwxrwxrwx 1 root root 10 Feb 21 08:58 wwn-0x600605b0057337c01df4874d2e7f5d6e-part2 -> ../../sda2
lrwxrwxrwx 1 root root 10 Feb 21 08:58 wwn-0x600605b0057337c01df4874d2e7f5d6e-part3 -> ../../sda3
lrwxrwxrwx 1 root root 10 Feb 21 08:58 wwn-0x600605b0057337c01df4874d2e7f5d6e-part4 -> ../../sda4
lrwxrwxrwx 1 root root 10 Feb 21 08:58 wwn-0x600605b0057337c01df4874d2e7f5d6e-part5 -> ../../sda5

/dev/disk/by-partlabel:
total 0
lrwxrwxrwx 1 root root 10 Feb 21 08:58 primary -> ../../sda5

/dev/disk/by-partuuid:
total 0
lrwxrwxrwx 1 root root 10 Feb 21 08:58 50aa8731-d319-49d6-93a6-591257a2aac0 -> ../../sda2
lrwxrwxrwx 1 root root 10 Feb 21 08:58 53a507f9-eccf-40a1-b90f-d48cf5227450 -> ../../sda5
lrwxrwxrwx 1 root root 10 Feb 21 08:58 5a62adf2-d3b4-45d5-abaa-1982f4195eaa -> ../../sda1
lrwxrwxrwx 1 root root 10 Feb 21 08:58 a356355d-7c41-41e9-b5db-0cd241a34339 -> ../../sda4
lrwxrwxrwx 1 root root 10 Feb 21 08:58 e4404197-fa71-4713-8151-3dced02c48e8 -> ../../sda3

/dev/disk/by-path:
total 0
lrwxrwxrwx 1 root root  9 Feb 14 14:42 pci-0000:00:1f.2-ata-1.0 -> ../../sr0
lrwxrwxrwx 1 root root  9 Feb 14 14:42 pci-0000:00:1f.2-scsi-1:0:0:0 -> ../../sr0
lrwxrwxrwx 1 root root  9 Feb 21 14:57 pci-0000:24:00.0-scsi-0:2:0:0 -> ../../sda
lrwxrwxrwx 1 root root 10 Feb 21 08:58 pci-0000:24:00.0-scsi-0:2:0:0-part1 -> ../../sda1
lrwxrwxrwx 1 root root 10 Feb 21 08:58 pci-0000:24:00.0-scsi-0:2:0:0-part2 -> ../../sda2
lrwxrwxrwx 1 root root 10 Feb 21 08:58 pci-0000:24:00.0-scsi-0:2:0:0-part3 -> ../../sda3
lrwxrwxrwx 1 root root 10 Feb 21 08:58 pci-0000:24:00.0-scsi-0:2:0:0-part4 -> ../../sda4
lrwxrwxrwx 1 root root 10 Feb 21 08:58 pci-0000:24:00.0-scsi-0:2:0:0-part5 -> ../../sda5

/dev/disk/by-uuid:
total 0
lrwxrwxrwx 1 root root 10 Feb 21 08:58 4272b75a-ea72-4068-8826-e2dfc5611fd5 -> ../../sda5
lrwxrwxrwx 1 root root 10 Feb 21 08:58 46f191b6-7472-49c0-bd98-75824020d947 -> ../../sda2
lrwxrwxrwx 1 root root 10 Feb 21 08:58 4ceac2e7-6bdc-40d2-9dff-da7a2099bf45 -> ../../sda4
lrwxrwxrwx 1 root root 10 Feb 21 08:58 B738-D576 -> ../../sda1
lrwxrwxrwx 1 root root 10 Feb 21 08:58 a5a2612d-d0cb-4b05-a3cf-cc95ecd0235b -> ../../sda3
ibmserver2:~ #

In my ignorance I cannot see clues but hope this helps. I just checked using yast and the strange name is still showing and I see it is there against sda5 which also has /data.

6

From /etc/fstab:

UUID=4272b75a-ea72-4068-8826-e2dfc5611fd5       /data   xfs     defaults 1 2

Which means that the partion wth that UUID contains a file system of type xfs and should be mounted in /data.

From /dev/disk/by-uuid:

lrwxrwxrwx 1 root root 10 Feb 21 08:58 4272b75a-ea72-4068-8826-e2dfc5611fd5 -> ../../sda5

Which means that that UUID is /dev/sda5.

From mount:

/dev/sda5 on /tmp/libstorage-iztF91/tmp-xfs-mp type xfs (rw,relatime,attr2,inode64,noquota)
/dev/sda5 on /data type xfs (rw,relatime,attr2,inode64,noquota)

Which means that the partition /dev/sda5 is indeed mounted on /data.
There is the second line abobe it which is the one that makes you worry. I have in fact no idea why it is there. But you must still be able to access the files on that file system using /data/…

Thus

ls -l /data

must show the directories/files at the bottom of that file system. Is that OK?

The fdisk -l shows that the size of sda5 is ~4.9 TB . Is that what it should be after your resizing?

Also you can check if the file system was also enlarged and now fills the new size:

df -h /data
7

Hi Henk,
Everything checks out except I am worried about the extra line. I think it is an artifact remaining from the resizeing but it should have been removed once process was completed. Partition size at 4.9TiB is correct.
Thanks for the help.
Regards,
Budgie2

8

I was also surprised and made some tests. It appears that with current Linux kernel it is possible to mount the same partition concurrently multiple times as long as mount options are the same. Still, this line looks like leftover from YaST partitioner and should not be present. Bug report makes sense.

9

I think I support his. Specialy when it does not go away after a reboot.

10

Hi Henk, “reboot” now there is a thought!!!

After a reboot the anomaly has gone.

Budgie2

11

Ahem, thus it is a relict leftover from the action.

In fact it was only an afterthought to mention “reboot”. I in fact had the impression (but having an impression is dangerous in debugging) that after some poking around and after a few days, you would have rebooted anyhow. In any case, when I would have done such a reorganisation, I would have rebooted, just to test if it still boots flawless.

Tnat is of course a lesson you learn when managing computer room systems. You should be as sure as possible that when it falls over in the night, it at least reboots and continues to serve the customer. Were it only for your own undisturbed sleep :wink: