Same target could be used by several filesystems with File backend #130

degremont · 2012-06-05T14:57:13Z

In File backend mode, shine install and format actions do not check if targets declared in a filesystem are available. By available, I mean free from any other filesystem configuration.
"shine status" detects this situation, though.
I don't know if the test can be done as early as "shine install" but, maybe "shine format" could display an error and exit, or at least prompt the user before resuming execution ?.

Reported by: theryf

degremont · 2012-06-05T20:34:26Z

        priority
            changed from major to minor

Replying to theryf:

"shine status" detects this situation, though.
I don't know if the test can be done as early as "shine install" but, maybe "shine format" could display an error and exit, or at least prompt the user before resuming execution ?.

shine status does active checking on target device and ensure that the current device is coherent with what is describe in the model.
shine format could be used to reformat an existing filesystem or replace a previous one by a new one. In this case it is normal that the current device is not coherent with what is described in shine configuration. It is impossible to "guess", by shine format, is what is present on the device is coherent or not.

In File backend mode, shine install and format actions do not check if targets declared in a filesystem are available. By available, I mean free from any other filesystem configuration.

The only place where this check could be done is in shine install. This means that the File backend mode should be improved with a cache, storing for each target if it is used or not. This should be kept coherent when storage.conf is modified. This is close to what a cluster DB backend does. However, this has side effect and cache coherency issue I'm not sure we want to be faced to.
We have to though about it but I'm not sure we will support this.