1 |
On 3/17/19 10:48 AM, Peter Humphrey wrote: |
2 |
> Hello list, |
3 |
|
4 |
Hi, |
5 |
|
6 |
> My little Atom box has a small rescue system which I boot once a week |
7 |
> to back up the main system. The backup script is a simple list of bash |
8 |
> commands to mount partitions and tar them to a USB disk. |
9 |
|
10 |
Please share a copy of the backup script. |
11 |
|
12 |
> While the backup is running I run another script to clean up after |
13 |
> any recent update, which involves removing surplus packages, running |
14 |
> eclean etc. |
15 |
|
16 |
Please share a copy of your cleanup script. |
17 |
|
18 |
> But! At least once per session I have to remount the root filesystem read- |
19 |
> write because something, presumably tar, has caused it to be remounted |
20 |
> read- only. |
21 |
|
22 |
"tar" itself shouldn't alter mounts at all. |
23 |
|
24 |
It is possible that there could be a mount option that causes the file |
25 |
system to be remounted read-only if there is a problem accessing the |
26 |
file system. |
27 |
|
28 |
> Where do I start tracking this down? This behaviour was a factor in |
29 |
> my suspecting an SSD failure, but I've replaced that and still get the |
30 |
> same remounting. |
31 |
|
32 |
But such remounting is not likely on a new SSD. |
33 |
|
34 |
I'd need to see the scripts to even hazard a guess as to what might be |
35 |
happening. |