Thanks for the reply, Greg. With traditional file system experience, I have to admit it will take me some time to get used to the way CephFS works. Considering it as part of my learning curve. :-)
One of concerns I have it that, without tools like fsck, how could we know the file system is still consistent? Even RADOS doesn't report error, could there be any miscommunication(e.g., due to bug, networking issue, disk bit flip, ...) between metadata operation and stripe I/O? For example, the first stripe of a file is created but its inode id(on RADOS) is wrong for some reason, and thus RADOS doesn't think it belongs to the correct file. This may never happen and I just use it here to explain my concern. Thanks, Brandon On Mon, Sep 15, 2014 at 3:49 PM, Gregory Farnum <g...@inktank.com> wrote: > On Mon, Sep 15, 2014 at 3:23 PM, brandon li <brandon.li....@gmail.com> > wrote: > > If it's true, is there any other tools I can use to check and repair the > > file system? > > Not much, no. That said, you shouldn't really need an fsck unless the > underlying RADOS store went through some catastrophic event. Is there > anything in particular you're worried about? > -Greg > Software Engineer #42 @ http://inktank.com | http://ceph.com >
_______________________________________________ ceph-users mailing list ceph-users@lists.ceph.com http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
