On Wednesday April 8, goswin-v-b@xxxxxx wrote:
> "NeilBrown" <neilb@xxxxxxx> writes:
> >
> > Why /var/run cannot be mounted from tmpfs nice and early too I don't know..
>
> Because /var is not yet mounted.
I guess that is a credible answer.
We really want "/volatile" rather than "/var" for holding "run" and
"locks".. and /tmp.
I guess that is rather unlikely to happen universally.
>
> Maybe mdadm should just have
>
> -m, --map <file>
> Filename of the map file for incremental operations. Defaults
> to /var/run/mdadm.map. Note that the default path might not exist
> or be read-only early in the boot process in which case a
> suitable alternative must be specified.
>
> Wouldn't that be more flexible?
>
> Debian could then set 'MAP /lib/init/rw' in its mdadm.conf.
Adding a config option because we cannot agree on a standard isn't my
idea of a good time...
I'm leaning towards:
- to open for reading, if /var/run/mdadm/map doesn't exist,
try /dev/.mdadm.map
- to open for writing, if opening /var/run/mdadm/map and
/var/run/mdadm.map for writing fails, try /dev/.mdadm.map
Note that I don't want to put the file in /dev/md/ as that might not
exist yet either.
So the idea is to still use /var/run/mdadm{.,/}map, but fall back on
/dev/.mdadm.map if that is the only option.
Thought?
NeilBrown
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
