Error when deleting shared folder

Ok, but does it also work like this if the physical drive does not exist any more.

Zitat von macom

Ok, but does it also work like this if the physical drive does not exist any more.

Usually but I haven't tried it lately. Worst case, follow what I recommended and if you can't delete the missing entry in the filesystems tab, THEN delete the mntent entry in config.xml. You should always be able to delete the shared folders from services and delete the shared folder itself.

Zitat von Buers

flmaxey: "Note that deconfiguring a drive must be done in the same order that it was configured, but in reverse order. "

Well, my drive died. It seems that OMV needs a working drive, to properly remove it? Of course, I may not have understood, how to do it.. When I try to remove the file system of the dead drive from shared folders, I get the errors described above. OMV shows me, that there are no references left to the shared folder. (I had removed CIFS/SMB references before).

Even with a missing drive, "de"configuring works with EXT4.
________________________________________________________

I just ran through the entire process in a VM:

1. Install a new drive
2. Create a file system. (EXT4)
3. Mount the file system
4. Create a shared folder (Music)
5. Create an Rsync Job that references the shared folder.
(Run the Rsync job to populate the shared folder with files)
6. Share the folder to the network with SMB/CIF
___________________________________________________________________________

I have the "Reset Perm's" plugin installed which provides the Shared Folder in Use tab in Access Rights Management, Shared Folders. (In the following: Ignore Music_R_OMV - that's a file system, on another server, added by Remote Mount .)

So, on the local Data drive;
- I have "Music", added as a shared folder.
- I referenced the shared folder, music, with an Rsync job.
- I put the shared folder on the network with SMB/CIF

I then removed the data drive - as in it's completely gone. Storage, File Systems shows it as "Missing".
___________________________________________________________________________

6. I deleted the SMB/CIF share - music.
5. I deleted the Rsync Job that references the music folder
4. I deleted the shared folder Music
3. I unmounted the file system (EXT4)
2. I deleted the file system.
1. The drive is already gone.

Using the screen above, at step 4, you'd need to remove all services, (Rsync, SMB, etc.) from each of your shared folders, then delete the shared folders themselves. Check Shared Folder in Use to insure all has been removed.

After that, you should look for any configured SMART TESTS set for the physical drive and SMART Monitoring. Delete those as well. After than, delete the file system. If the drive is still in the machine, in Physical drives, wipe it or physically remove (if you haven't already).

I understand this is the process it is supposed to be.

But as I understood the point of this thread is, that the drive is not there any more. As far as I understand the process is working like this only to a certain point in case the drive is not there any more.

Zitat von buers

Well, my drive died. It seems that OMV needs a working drive, to properly remove it? Of course, I may not have understood, how to do it.. When I try to remove the file system of the dead drive from shared folders, I get the errors described above. OMV shows me, that there are no references left to the shared folder. (I had removed CIFS/SMB references before).

As noted, in the above exercise, the drive was not there either. (As in deleted, gone, and missing on the file system page.)

The drive doesn't have to exist to delete the file system associated with it. However, to delete the file system, references to the drive can not exist.
______________________________________________

Even with "Status" Missing, if "Referenced" is No; the Delete button should be available. If the Delete button is not available, that's not normal behavior. Perhaps there's a fix or patch for this ( @ryecoaaron 's advice above) but, as a matter of preference, I'd consider rebuilding to insure the install is clean and clear of other potential issues.

Zitat von flmaxey

As noted, in the above exercise, the drive was not there either.

Missed that, sorry.

Zitat von macom

Missed that, sorry.

It's all good!

Let's hope that @buers finds a reference to delete.

Zitat von buers

I did. Or perhaps I do misunderstand, what you mean. Maybe you can have a look at the screenshot in post #16.

I wasn't telling you what you needed to do. I was answering macom's general question about removing things in this situation since he tagged me (I didn't read the whole thread). Your screenshot says it isn't referenced. So, no shared folders should need to be deleted. If the delete button in the filesystems tab doesn't work, you need to remove the mntent entry manually.

Zitat von buers

But, when I delete this, there would be a stale sharedfolder entry be left

When the filesystem says it isn't referenced, there *shouldn't* be any sharedfolders pointing to it. Your system is in a weird state if that is the case.

Zitat von buers

So, to me it looks wrong, to delete the mntent. After all, I was not Abel to delete/remove the shared folder.

If there is a sharedfolder pointing at it, delete the mntent entry and sharedfolder entry from config.xml.

Zitat von buers

Anyway: how to delete it? Just edit config.xml with vi? I would expect, that services or something else must be stopped or restarted or something similar.

Yes, just edit it with whatever editor you like. Unless the sharedfolder is referenced by a service, you don't need to restart any services. If the sharedfolder is referenced by services/plugins, you would need to remove those first. I would execute omv-mkconf fstab after removing the mntent entry. Make a backup of config.xml before you edit anything. If you do something wrong, copy the file back in. And config.xml isn't continually referenced by services. It is just used to populate the web interface and then used to write config files when told to update them.

While I'll concede that there may be a real problem - it only takes 1 reference of some kind to prevent deleting the file system and, after that, the drive. Since that means finding the reference(s) or a rebuild, it doesn't hurt to ask and one reference is easy to miss.
______________________________________________________

First, go to System, Plugins and find the openmediavault-resetperms plugin. Install it.

After the plugin is installed, then you'll have the "Shared Folder in Use" tab, as shown in the post above. If you have any services attached to shared folders that are gone, again as shown, you'll have an indication of where to go to find the service and delete it. In the example, there was an Rsync job (requires that the appropriate configured job under Services, Rsync be deleted), a SMB network share (required that the appropriate network share under Services, SMB/CIF be deleted), and finally the shared folder itself.

(**But,, the shared folder itself, where you got your error, can't be deleted until all services attached to it are gone.**)

Depending on what you configured on the missing drive, there may be several items to remove.
_______________________________________________________________

Beyond the above:

What file system was the dead drive using?
If you were using anything that required a plugin, such as ZFS or UnionFS, it might be necessary to delete and reinstall the plugin.

Also, other plugins like LVM, rsnapshot, disk encryption, etc., can reference a file system and hold it.

Zitat von buers

You are certainly the better expert for OMV than me. But anyway, can you please recheck your answer. Seems you were missing one level of reference in the hierarchy in your answer.

@ryecoaaron doesn't miss much and he is the expert in this subject and most others like it - like "Linux" in general. And he's even a good excellent electrician. (I had to edit "good". In addition to Phase Angle Theta and a Power factor of 1, theory stuff, he knows how to wire like an artist. )

Zitat von buers

Services (like SMB) do reference shared folders.
When the Shared folders are not referenced anymore by any services, the Shared folder tab (like in my screenshot) show a "No" under references. Please note, that your sentence starts with "filesystem" while my screenshot (which you where refering to) was about shared folders.

There is a hierarchy involved. (And while it may not apply to you, for others who may read this thread.)

Physical Drive
- (Physical drive services like SMART tests and monitoring)
- (Volume & sub-volume types, if any (LVM, RAID, etc.)
File system
- (file system services like encryption)
Share
- share only services, if any (like rsnapshot)
Services (Rsync, SMB)
__________________________________________________________________________

NTFS on an external drive - that's a wild card,, and when you say you had an NFS share based on an NTFS drive share.... While I don't use NFS now, I had an experience where an NFS share just wouldn't go away.

Also, there's your upgrade to consider. Going from OMV 3 to 4, especially if this problem existed in OMV3... Rebuilding, sometimes, makes sense. From a time standpoint alone, a rebuild is better than chasing a phantom problem.

Here's to hoping that it works out for you but, if it doesn't and you have to rebuild, consider booting on a USB drive and cloning your boot drive. How to do that (a USB boot drive and cloning) is in this guide.

If you rebuild, I'd unplug your data drive, build your boot drive and when all is updated and healthy, plug in and mount the data drive. The content, in your various folders, will still be there.

Zitat von buers

But anyway, can you please recheck your answer. Seems you were missing one level of reference in the hierarchy in your answer.

What level am I missing? Shared folders can be referenced and filesystems can be referenced. You didn't mention a problem removing a shared folder from a service. So, I didn't mention that step.

Zitat von buers

I removed all Services. After that I expect, that there are still shared folders left in config.xml. But there are no references left to that shared folder. Seems no contradiction to me at all.
Only removing the Shared folder (as described in detail in post #34) would remove the sharedfolder inside config.xml from my logic. So it is no surprise to me (as opposed to your arguing in #33), that at this time, sharedfolder is still left in config.xml.
Please correct, where I went wrong.

I am very confused by what you are asking. When you remove the sharedfolder from services, that process does not delete sharedfolder itself and of course there is still a sharedfolder entry in config.xml. It will only be removed when you delete it. Since your system was running into an error when trying to delete it, I said delete the entry in config.xml. Once all sharedfolders are deleted that reference a filesystem, then you can delete that filesystem. I really don't like when people have to edit config.xml.

Zitat von buers

Did anybody have a look at the error messages of post #1 and can explain them?

Yes. The error with the mount unit when trying to delete the sharedfolder is *probably* caused by something still in use or the mount unit failing to mount something that doesn't exist (they don't like missing hardware). Most things in most OSes don't like when hardware is configured and then it disappears.