On Friday, 12 January 2018 13:28:39 GMT Rich Freeman wrote:
> There is no need to run eject on a USB drive - just pull the thing and
> udev will clean up the device nodes.
One other small point: I've found that running eject on a USB drive on, say,
/dev/sda marks /dev/sda unavailable for
On January 12, 2018 10:58:17 AM GMT+01:00, Adam Carter
wrote:
>>
>> I replaced it with a USB3 drive, so I needed to update the udev rules
>> that automatically mount it and then "umount" it when it's removed.
>>
>
>Pretty sure you'd risk filesystem corruption by not
On Fri, Jan 12, 2018 at 6:39 AM, Mick wrote:
> On Friday, 12 January 2018 09:58:17 GMT Adam Carter wrote:
>>
>> Pretty sure you'd risk filesystem corruption by not umounting before you
>> remove the device. Did it used for force an fsck on each mount because the
>>
On Friday, 12 January 2018 09:58:17 GMT Adam Carter wrote:
> > I replaced it with a USB3 drive, so I needed to update the udev rules
> > that automatically mount it and then "umount" it when it's removed.
>
> Pretty sure you'd risk filesystem corruption by not umounting before you
> remove the
>
> I replaced it with a USB3 drive, so I needed to update the udev rules
> that automatically mount it and then "umount" it when it's removed.
>
Pretty sure you'd risk filesystem corruption by not umounting before you
remove the device. Did it used for force an fsck on each mount because the
[This has nothing to do specifically with Gentoo.]
What cleanup actions would you have put in a script to be triggered by
udev when a USB or Firewire backup drive has been unplugged?
The external Firewire drive I used for nightly backups died yesterday.
I replaced it with a USB3 drive, so I
6 matches
Mail list logo