Re: [Bug 1681410] Re: fstrim corrupts ocfs2 filesystems when clustered

2017-08-01 Thread Kyle O'Donnell
I tried disabling fstrim on all but one server and had the exact same issue as I did when cron enabled it on all servers. - Original Message - From: "Nick Stallman" <1681...@bugs.launchpad.net> To: "Kyle O'Donnell" <ky...@0b10.mx> Sent: Tuesday, August

[Bug 1681410] Re: fstrim corrupts ocfs2 filesystems when clustered

2017-04-10 Thread Kyle O'Donnell
It is one device. We have 2 luns for 2 different ocfs2 filesystems mounted on all servers (6) in the cluster. It is presented via fiber channel from our SAN. I think the issue is that if you run fstrim from all servers which are mounting the same ocfs2 filesystem at the same time, bad stuff

[Bug 1681410] [NEW] fstrim corrupts ocfs2 filesystems when clustered

2017-04-10 Thread Kyle O'Donnell
Public bug reported: Recently upgraded from trusty to xenial and found that our ocfs2 filesystems, which are mounted across a number of nodes simultaneously, would become corrupt on the weekend: [Sun Apr 9 06:46:35 2017] OCFS2: ERROR (device dm-2): ocfs2_validate_gd_self: Group descriptor

[Bug 1358226] Re: kernel and lockd xprt_adjust_timeout rq_timeout

2015-03-17 Thread Kyle O'Donnell
looks like this made it into 3.13.0-48.80 https://launchpad.net/ubuntu/trusty/+source/linux/+changelog * LOCKD: Fix a race when initialising nlmsvc_timeout https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1427438 Upgraded a few days ago, haven't seen the errors -- You received this bug

[Bug 1358226] Re: kernel and lockd xprt_adjust_timeout rq_timeout

2015-01-19 Thread Kyle O'Donnell
Does anyone know if/when this will make it into the trusty kernel? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1358226 Title: kernel and lockd xprt_adjust_timeout rq_timeout To manage

[Bug 1358226] Re: kernel and lockd xprt_adjust_timeout rq_timeout

2015-01-05 Thread Kyle O'Donnell
Looks like there may be a patch http://www.spinics.net/lists/linux-nfs/msg48575.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1358226 Title: kernel and lockd xprt_adjust_timeout rq_timeout

[Bug 1376245] Re: remove_proc_entry+0x139/0x1b0() -- name 'fs/nfsfs'

2014-10-17 Thread Kyle O'Donnell
We have this same problem. Just upgraded to -38 , no change: [184207.109594] [ cut here ] [184207.109604] WARNING: CPU: 15 PID: 10701 at /build/buildd/linux-3.13.0/fs/proc/generic.c:511 remove_proc_entry+0x139/0x1b0() [184207.109606] name 'fs/nfsfs' [184207.109608]

[Bug 1356809] [NEW] unable to load nvidia kernel module in kernels newer than3.13.0-30

2014-08-14 Thread Kyle O'Donnell
Public bug reported: I've tried using -31,-32 and -33 revisions of the kernel and eahc time i am unable to load the kernel module, it errors with some kind of drm message (when i have time to upgrade and provide debug info i will update this bug ** Affects: nvidia-graphics-drivers-331-updates