| 1 |
On Tue, Feb 16, 2016 at 01:22:13PM -0500, Rich Freeman wrote: |
| 2 |
> On Tue, Feb 16, 2016 at 1:05 PM, William Hubbs <williamh@g.o> wrote: |
| 3 |
> > |
| 4 |
> > The reason it exists is very vague to me; I think it has something to do |
| 5 |
> > with claims of data loss in the past. |
| 6 |
> > |
| 7 |
> |
| 8 |
> Is there some other event that will cause all filesystems to be |
| 9 |
> remounted read-only or unmounted before shutdown? |
| 10 |
|
| 11 |
When localmount/netmount stop they try to unmount file systems they know |
| 12 |
about, but they do not try to remount anything. |
| 13 |
|
| 14 |
|
| 15 |
> You definitely will want to either unmount or remount readonly all |
| 16 |
> filesystems prior to rebooting. I don't think the kernel guarantees |
| 17 |
> that this will happen (I'd have to look at it). Just doing a sync |
| 18 |
> before poweroff doesn't seem ideal - if nothing else it will leave |
| 19 |
> filesystems marked as dirty and likely force fscks on the next boot |
| 20 |
> (or at least it should - if it doesn't that is another opportunity for |
| 21 |
> data loss). |
| 22 |
> |
| 23 |
> There are different ways of accomplishing this of course, but you |
| 24 |
> really want to have everything read-only in the end. |
| 25 |
|
| 26 |
unmounting is easy enough; we already do that. |
| 27 |
|
| 28 |
What I'm trying to figure out is, what to do about re-mounting file |
| 29 |
systems read-only. |
| 30 |
|
| 31 |
How does systemd do this? I didn't find an equivalent of the mount-ro |
| 32 |
service there. |
| 33 |
|
| 34 |
William |
Archives