Hi Jan...
Thank for the reply.
Yes, I did an 'umount -l' but I was sure that no I/O was happening at
the time. So, I was almost 100% sure that there were no real incoherence
in terms of open files in the OS.
On 08/20/2015 07:31 PM, Jan Schermer wrote:
Just to clarify - you unmounted the filesystem with "umount -l"? That
almost never a good idea, and it puts the OSD in a very unusual
situation where IO will actually work on the open files, but it can't
open any new ones. I think this would be enough to confuse just about
any piece of software.
Yes, I did an 'umount -l' but I was sure that no I/O was happening at
the time. So, I was almost 100% sure that there were no real incoherence
in terms of open files in the OS.
Was journal on the filesystem or on a separate partition/device?
The journal in on the same disk, but in a different partition.
It's not the same as R/O filesystem (I hit that once and no such havoc
happened), in my experience the OSD traps and exits when something
like that happens.
It would be interesting to know what would happen if you just did rm
-rf /var/lib/ceph/osd/ceph-4/current/* - that could be an equivalent
to umount -l, more or less :-)
Will try that today and report back here.
Cheers
Goncalo
_______________________________________________
ceph-users mailing list
ceph-users@lists.ceph.com
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
