Messages in this thread | | | Date | Fri, 17 Sep 2010 11:53:19 +0200 | From | Tejun Heo <> | Subject | Re: ahci rmmodable and shouldn't |
| |
Hello,
On 09/16/2010 11:58 PM, Randy Dunlap wrote: >> `rmmod ahci' works even if the module is being used (`lsmod' thinks it's >> not being used but rmmoding ahci triggers filesystem erros and I've to >> force a reboot). >> >> I've been told it's the same as plugging a cable. IMO that's what >> /sys/stuff/eject_or_similar is to, not `rmmod ahci'. >> >> >> I *assume* it was caused by the split between libahci & ahci, since in >> 2.6.32 >> `rmmod ahci' is impossible because it's marked as being in use. Didn't try >> `rmmod -f ahci' but that's not the point. >> >> >> I'm posting again about this because it doesn't make sense to me the >> actual behaviour.
Just don't rmmod a module which is serving a live filesystem. Why does it even matter?
-- tejun
| |