On Mon, 15 Oct 2012, Adam Nielsen wrote: > > The immediate cause of the problem is that the osd's "commit_op_seq" file is > > reading back '0', > > which is invalid; it's created with an initial value of 1. Try removing the > > osd data dir > > (/var/lib/ceph/osd/ceph-0) completely and let it be recreated; perhaps > > something got there somehow by mistake. > > Well it looks like commit_op_seq was never created properly: > > $ ls /var/lib/ceph/osd/ceph-0/current/ > total 4.0K > drwxr-xr-x 1 root root 26 Oct 14 17:40 . > drwxrwx--- 1 root root 74 Oct 14 17:40 .. > -rw-r--r-- 1 root root 0 Oct 14 17:40 commit_op_seq > > But how do I delete it to start again? > > $ rm -rf current/ > rm: cannot remove `current': Directory not empty > $ ls current/ > total 4.0K > drwxr-xr-x 1 root root 0 Oct 15 09:16 . > drwxrwx--- 1 root root 26 Oct 15 09:16 .. current/ is a btrfs subvolume.. 'btrfs sub delete current' will remove it. > This is on a brand new btrfs filesystem mounted in /var/lib/ceph/osd/ceph-0. I > created it with this: > > $ mkfs.btrfs -L data -s 4096 /dev/sda1 > > Did I do something wrong? The warning in the previous email suggets you're running a fairly old kernel.. there is probably something handled incorrectly during the fs init process. Exactly which kernel are you running? In any case, btrfs isn't going to work particularly well on something that old; I suggest running something newer (3.5 or 3.6) or switching to XFS. 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
