Vratislav Podzimek
Vratislav Podzimek
See also #584
I think it makes sense to add a new `mkfs.extra_opts` option to the [`UDisks2.Block.Format()` method](http://storaged.org/doc/udisks2-api/latest/gdbus-org.freedesktop.UDisks2.Block.html#gdbus-method-org-freedesktop-UDisks2-Block.Format) that would allow passing arbitrary extra options for the *mkfs* command. Adding them one by...
Not sure what the right thing to do is here. Implicitly deactivating the VG or in general arbitrary storage stack on the unlocked LUKS device is a potentially dangerous operation....
> Assuming that udisks is asked to lock the disk, what are the dangers of trying to (always) deactivate the volume group connected to a contained physical volume? (Not forcibly,...
> With that logic, how can udisks ever unlock a crypted volume? You mean **lock**, I guess? Well, trying to do what `cryptsetup close` would do is one thing, trying...
IIRC, this is being done for some other file systems too, but these don't support POSIX ownership at all, I think. What happens if files **have** ownership and the suggested...
> For removable disk devices does not make much sense to use or store uid/gid information, nor to enforce it. I don't think this is necessary the case. I mean,...
That's what I kind of expected.
Thanks for the heads up, this is really an interesting issue! Surely there needs to be a system-wide solution *udisks* should adapt to.