On Feb 23, 2012, Sage Weil <[email protected]> wrote: > On Tue, 21 Feb 2012, Alexandre Oliva wrote: >> This was supposed to fix bug 1946, and likely bug 1849 too, but it looks >> like something's still missing for a complete fix. fuse-unmounting >> between touching a dir and creating a snapshot seems to help get correct >> snapshot timestamp,
> Hmm, that sounds like ceph-fuse isn't sending the write flushsnap cap > message. I forget.. have you tried the same with the kernel client? Not recently enough that I'd remember exactly what I did. However, I don't see how ceph-fuse could be the problem, given today's experiments. Here's what I just did (all with fuse): create snapshot check timestamps -> baseline unmount mount again check timestamps -> same restart mds check timestamps -> same unmount mount again check timestamps -> same moved a tree into dir check timestamps -> dir changed and snapshot unchanged, as expected unmount mount again check timestamps -> same restart mds check timestamps -> snapshot changed to dir's; its size too! After each umount, I checked that ceph-fuse was no longer running (it sometimes remains running for a while after umount completes) I've got full mds logs for this session, but they're kind of huge (860M). Please remind me how to upload them to your server. -- Alexandre Oliva, freedom fighter http://FSFLA.org/~lxoliva/ You must be the change you wish to see in the world. -- Gandhi Be Free! -- http://FSFLA.org/ FSF Latin America board member Free Software Evangelist Red Hat Brazil Compiler Engineer -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
