Haiku does not update name of a renamed volume until after a reboot

[scottmc]

I have three install from volume listed in the Install from button, but two of them were called "Haiku". To make sure that I was installing from the right one I renamed one of the volumes, but even closing installer and restarting it still showed the old names. Only after a system reboot did the new volume name show up. This was on 25002. I'll check on a fresher build soon.

[scottmc]

This isn't just an Installer issue. Doing an ls / it still lists the old name given to the newly renamed volume. After a restart ls / then shows the new name. You would assume that when you rename something that it gets renames when you do it and shouldn't have to wait till after a reboot for it to show up. Changing the summary to reflect this, as it's not a bug in Installer. If you reint a drive in drive setup under Installer and give it a different name there, it DOES get picked up just fine with the new name in Installer. The problem happens if you right-click on a volume and then "edit name". If you try to rename a volume and then rename it back to the name it had before you get an error saying that name already exists! So it seems it's not updating when you expect it to be.

[bga]

As the other bug was marked a duplicate of this one, Haiku should also update the mount point (when the mount point is automatically created by, say, Tracker) as a user usually will expect to find the mount point at /VolumeName.

[jonas.kirilla]

This issue is still there in hrev32840. DriveSetup and the mount menus don't pick up on volumes getting renamed. Closing and reopening DriveSetup doesn't help. I suppose this is an issue with the DiskDeviceManager.

bga: Mountpoints for BFS volumes get updated now but I think not those of FAT volumes.

(BTW, I have a volume where dosfs_wfsstat detects a "label mismatch" which appears to block renaming it.)

[axeld]

(In #4833) The hang is probably a duplicate of #4223. Please alway only mention one bug per ticket.

[scottmc]

This is still with us in hrev41287. To check, rename a volume and then run installer, installer still shows the previous volume name.

[bonefish]

I suppose the problem is that the file system implementations don't notify the disk device manager (DDM) that the name changed. E.g. bfs_write_fs_stat() changes BFS's internal/on-disk data structures, but doesn't tell the DDM. It would have to get the corresponding KPartition and call SetName() on it.

[scottmc]

This one still exists.

[waddlesplash]

Indeed it does. I ran into it just last week myself while testing out the NTFS driver.