Quoting Mike Kupfer (m.kup...@acm.org): > It's a journaled (ext3) filesystem, so when I next mounted it, it just > recovered the journal. e2fsck give me
> smartctl --health reports no problems. Though I don't know the smartmon > tools well; if there's some other check that makes sense to run, I'm > certainly open to suggestions. > I thought those were a direct consequence of the disconnect, though I > don't know what the kernel was trying to write out. I don't think I was > actively using the Iomega drive when I plugged in the thumb drive. That all looks good then. I'm guessing udisksd tried to do something. I've never seen anything like that pop up on my system. I grepped my logs for udisks and see stuff like /var/log/daemon.log: avahi-daemon[783]: Loading service file /services/udisks.service. /var/log/daemon.log: avahi-daemon[783]: Service "west" (/services/udisks.service) successfully established. avahi was, and udisks now is, a complete mystery to me. How do you pronounce avahi anyway, like Hi Ava! or something more latin. Cheers, David. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150312200307.gg7...@alum.home
