| 1 |
On 2018-01-12, Rich Freeman <rich0@g.o> wrote: |
| 2 |
> On Fri, Jan 12, 2018 at 6:39 AM, Mick <michaelkintzios@×××××.com> wrote: |
| 3 |
>> On Friday, 12 January 2018 09:58:17 GMT Adam Carter wrote: |
| 4 |
>>> |
| 5 |
>>> Pretty sure you'd risk filesystem corruption by not umounting |
| 6 |
>>> before you remove the device. |
| 7 |
|
| 8 |
That's why I don't do that. |
| 9 |
|
| 10 |
> This is all somewhat orthogonal to your original question though - |
| 11 |
> these are all things that you ought to do before you remove the |
| 12 |
> device, not after. |
| 13 |
|
| 14 |
Quite. |
| 15 |
|
| 16 |
> One thing I tend to do with scripts for backups to external devices |
| 17 |
> that I don't intend to leave mounted is build the mount and umount |
| 18 |
> into the backup script itself. |
| 19 |
|
| 20 |
Good point. That's probably what I should be doing instead of having |
| 21 |
udev mount the drive when it's plugged in. I think I'll work on that |
| 22 |
in my spare time. If I label the partition in question, it should be |
| 23 |
pretty simple... |
| 24 |
|
| 25 |
> I usually also include a check to ensure that some file/directory |
| 26 |
> exists which I expect to be on the drive, which prevents the backup |
| 27 |
> script from dumping a full backup into your mountpoint if it isn't |
| 28 |
> mounted (possibly on a filesystem with insufficient space - |
| 29 |
|
| 30 |
Yep, that's being done. The backup won't attempt to run if the |
| 31 |
external drive isn't mounted. |
| 32 |
|
| 33 |
-- |
| 34 |
Grant Edwards grant.b.edwards Yow! Inside, I'm already |
| 35 |
at SOBBING! |
| 36 |
gmail.com |
Archives