Maybe some strange errata caused my memory corruption if your not using ECC ram. You should check dmesg to see if there are any messages giving a clue to what went wrong. using an errors=remount may help in the future if the error was detectable but probably not necessary if this is such a rare occurrence.
On 05/19/2018 09:09 PM, John Jason Jordan wrote: > On Sat, 19 May 2018 19:55:52 -0700 > Thomas Groman <[email protected]> dijo: > >> It is saying some sort of IO error occurred when trying to get the >> current working directory. If you have already made sure that directory >> exists you should check the consistency of your disks. I remember >> having similar errors when working with disks with bad sectors and >> floppy disks. > I tried all kinds of things, and when I tried e2fsck it said that I > needed to umount it first, so I did. But then, before running e2fsck, it > occurred to me to try to re-mount it and then try my rsync > command again. Voilà! It is running as I write this. > > The strange part is that it was definitely mounted, but rsync didn't > think it was, How can something be mounted but not really mounted? Oh > well. Another of life's mysteries that I will probably never grok. > _______________________________________________ > PLUG mailing list > [email protected] > http://lists.pdxlinux.org/mailman/listinfo/plug _______________________________________________ PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
