Hi, That looks like a bug, ERESTARTSYS is not a valid error condition for write(). http://pubs.opengroup.org/onlinepubs/9699919799/ -- Eino Tuominen > Vedran Furač <vedran.furac@xxxxxxxxx> kirjoitti 23.7.2015 kello 15.18: > > Hello, > > I'm having an issue with nginx writing to cephfs. Often I'm getting: > > writev() "/home/ceph/temp/44/94/1/0000119444" failed (4: Interrupted > system call) while reading upstream > > looking with strace, this happens: > > ... > write(65, "e\314\366\36\302"..., 65536) = ? ERESTARTSYS (To be restarted) > > It happens after first 4MBs (exactly) are written, subsequent write gets > ERESTARTSYS (sometimes, but more rarely, it fails after first 32 or > 64MBs, etc are written). Apparently nginx doesn't expect this and > doesn't handle it so it cancels writes and deletes this partial file. > > Is it possible Ceph cannot find the destination PG fast enough and > returns ERESTARTSYS? Is there any way to fix this behavior or reduce it? > > Regards, > Vedran > > > > _______________________________________________ > ceph-users mailing list > ceph-users@xxxxxxxxxxxxxx > http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com _______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
 |