I'm not talking about IO happening, I'm talking about file descriptors staying open. If they weren't open you could umount it without the "-l". Once you hit the OSD again all those open files will start working and if more need to be opened it will start looking for them... Jan > On 24 Aug 2015, at 03:07, Goncalo Borges <goncalo@xxxxxxxxxxxxxxxxxxx> wrote: > > 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@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
 |