| 1 |
Jesús Guerrero wrote: |
| 2 |
> On Sun, August 30, 2009 21:38, Dirk Heinrichs wrote: |
| 3 |
> |
| 4 |
>> Am Sonntag 30 August 2009 19:29:39 schrieb Alex Schuster: |
| 5 |
>> |
| 6 |
>> |
| 7 |
>> |
| 8 |
>>> I have to change the bus from usb to scsi, then it works. But what |
| 9 |
>>> about unmounting? Is is possible to have it unmounted after I pull the |
| 10 |
>>> memory stick? |
| 11 |
>>> |
| 12 |
>> How do want to umount something that's not there anymore? You have to |
| 13 |
>> umount _before_ you pull it. |
| 14 |
>> |
| 15 |
> |
| 16 |
> You can force the umount using -l (no, it's not documented in the man |
| 17 |
> page). You can use this to umount a volume *after* it has been physically |
| 18 |
> removed. And some people use this crap on udev rules to remove the |
| 19 |
> volume when they unplug the pendrive. Then they wonder why the heck |
| 20 |
> the file is not where it should be. I guess they never heard of cached |
| 21 |
> writes. |
| 22 |
> |
| 23 |
> The correct thing to do is of course to umount it before, |
| 24 |
> and then unplug it or whatever. |
| 25 |
> |
| 26 |
> If you truly want to umount after, you should at least do a sync before |
| 27 |
> removing the device. In any case, if you don't follow the logical |
| 28 |
> order of the things don't complain if then you find that the files that |
| 29 |
> should be there are not there when you need them. |
| 30 |
> |
| 31 |
> If you truly love risk, just use umount -l, but you have to promise not |
| 32 |
> to cry if the fs breaks or your files are not writen when you sudenly |
| 33 |
> unplug the device. |
| 34 |
> |
| 35 |
> |
| 36 |
|
| 37 |
Basically, if he is going to do this the way he is thinking of doing it, |
| 38 |
use cp NOT mv. o_O If he uses mv and then unpkugs it without |
| 39 |
unmounting or syncing, the file is gone for good. At least with cp you |
| 40 |
still have the original file. |
| 41 |
|
| 42 |
Just thinking this through a little here. |
| 43 |
|
| 44 |
Dale |
| 45 |
|
| 46 |
:-) :-) |
Archives