I have also seen this on occasion when I unmount client, rebuild, then mount client all without rebooting client. I have done so much that I cannot for sure say what the exact conditions were, but I know I have gotten it when rebuilding an unmounted fs. Passing the "fsid=" mount option with the new fsid gets around it if I recall. On Mon, Aug 22, 2011 at 10:43 PM, Sage Weil <sage@xxxxxxxxxxxx> wrote: > On Mon, 22 Aug 2011, Jojy Varghese wrote: >> Hi >> I am getting "libceph: bad fsid, had >> e49ae577-0f7b-24e0-1c75-10ae17d9f86b got >> 3c9b15ef-c2d0-1318-4d12-3508025ccd97" on attempting to mount the fs. >> Any quick fixes? > > This means the client is getting data from a different file system than it > originally mounted. Probably you had the client mounted, rebuilt the fs > and restarted the monitors, and now the client is confused because the > servers were changed out from underneath it. > > sage > -- > To unsubscribe from this list: send the line "unsubscribe ceph-devel" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html > -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
