Re: [ceph-users] cephfs ceph: fill_inode badness

2015-12-06 Thread Don Waterloo
kernel driver. One node is 4.3 kernel (ubuntu wily mainline) and one is 4.2 kernel (ubuntu wily stock) I don't believe inline data is enabled (nothiing in ceph.conf, nothing in fstab). Its mounted like this: 10.100.10.60,10.100.10.61,10.100.10.62:/ /cephfs ceph

Re: [ceph-users] cephfs ceph: fill_inode badness

2015-12-06 Thread Yan, Zheng
On Sun, Dec 6, 2015 at 7:01 AM, Don Waterloo wrote: > Thanks for the advice. > > I dumped the filesystem contents, then deleted the cephfs, deleted the > pools, and recreated from scratch. > > I did not track the specific issue in fuse, sorry. It gave an endpoint >

Re: [ceph-users] cephfs ceph: fill_inode badness

2015-12-06 Thread Yan, Zheng
On Mon, Dec 7, 2015 at 12:52 AM, Don Waterloo wrote: > kernel driver. One node is 4.3 kernel (ubuntu wily mainline) and one is 4.2 > kernel (ubuntu wily stock) > > I don't believe inline data is enabled (nothiing in ceph.conf, nothing in > fstab). > > Its mounted like

Re: [ceph-users] cephfs ceph: fill_inode badness

2015-12-05 Thread Don Waterloo
Thanks for the advice. I dumped the filesystem contents, then deleted the cephfs, deleted the pools, and recreated from scratch. I did not track the specific issue in fuse, sorry. It gave an endpoint disconnected message. I will next time for sure. After the dump and recreate, all was good.

Re: [ceph-users] cephfs ceph: fill_inode badness

2015-12-04 Thread Yan, Zheng
On Fri, Dec 4, 2015 at 10:39 AM, Don Waterloo wrote: > i have a file which is untouchable: ls -i gives an error, stat gives an > error. it shows ??? for all fields except name. > > How do i clean this up? > The safest way to clean this up is create a new directory, move

[ceph-users] cephfs ceph: fill_inode badness

2015-12-03 Thread Don Waterloo
i have a file which is untouchable: ls -i gives an error, stat gives an error. it shows ??? for all fields except name. How do i clean this up? I'm on ubuntu 15.10, running 0.94.5 # ceph -v ceph version 0.94.5 (9764da52395923e0b32908d83a9f7304401fee43) the node that accessed the file then