similar to: [PATCH] undetected bug in smbfs kernel module ?

Hi, there appears to be a bug w.r.t. chown and quotas in ext3. In particular, if you "chown" a file on a filesystem with userquotas enabled, the quota charge in not transfered. ditto "chgrp" and group quotas. This happens because i_op->setattr has been redefined for files, and ext3_setattr doesn't do the DQUOT_TRANSFER like it should. I have fixed it by adding a

Hi, A system running ext3 crashed this afternoon (nothing to do with ext3, bad network driver). Is was saving a file from emacs when it happened. The file system is 0.06b and had ordered data as the mount option. Let me emphasize this was running ext3 pure, not with SnapFS or InterMezzo layered on top of it. strace reveals that Emacs does open("existing file name", O_TRUNC |

Hi, the first four patches in this series fix locking problems in OCFS2 quota code (three of them can lead to potential deadlocks). The fifth patch reorders ip_alloc_sem for directories to be acquired before localalloc locks. Mark would you please merge these? The last two patches implement lockdep annotations for OCFS2 cluster locks. We annotate all the cluster locks except for special ones

Hi, I'm resending this patch series. It's rediffed against linux-next branch of Joel's git tree. The first four patches are obvious fixes of deadlocks in quota code and should go in as soon as possible. The other three patches implement lockdep support for OCFS2 cluster locks. So you can have a look whether the code make sence to you and possibly merge them. They should be NOP when

Hello, the following series of patches fixes some issues with OCFS2 quotas. The first patch modifies VFS quota locking, the next patch uses the fact to simplify OCFS2 quota locking and solves a few deadlock issues. The third and the fourth patches fix another possible deadlocks in OCFS2 quota code and the last patch is a minor cleanup. Honza

The patch below makes some needlessly global functions static. diffstat output: fs/smbfs/inode.c | 2 +- fs/smbfs/proc.c | 6 +++--- fs/smbfs/proto.h | 5 ----- fs/smbfs/request.c | 6 ++++-- 4 files changed, 8 insertions(+), 11 deletions(-) Signed-off-by: Adrian Bunk <bunk@stusta.de> --- linux-2.6.10-mm1-full/fs/smbfs/proto.h.old 2005-01-04 00:57:42.000000000 +0100

https://bugzilla.samba.org/show_bug.cgi?id=10295 Summary: do_lchown() after set_xattr() causes xattrs to be dropped on Linux 3.10.20. Product: rsync Version: 3.1.0 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 Component: core AssignedTo: wayned at

If it is that bug that you're referencing, besides obviously upgrading, you could try to patch it yourself. Whether or not you need to patch this, probably depends on whether or not your users are actually seeing issues. All that seems to happen is that it's entering a failure case when it hasn't actually failed. https://www.samba.org/samba/patches/ Cheers, Garming On 04/07/16

Since upgrading S4 DCs I am see the following message in log.samba - DsCrackNames: Unsupported operation requested: FFFFFFF8DsCrackNames: Unsupported operation requested: FFFFFFF8Unable to fetch value for secret BCKUPKEY_13bb48fc-0844-4736-9972-e26453333856, are we an undetected RODC? DsCrackNames: Unsupported operation requested: FFFFFFF8DsCrackNames: Unsupported operation requested:

On Mon, 19 Sep 2016 10:50:25 -0400 Adam Tauno Williams via samba <samba at lists.samba.org> wrote: > On Mon, 2016-09-19 at 10:45 -0400, Adam Tauno Williams via samba > wrote: > > Since upgrading S4 DCs I am see the following message in log.samba - > > The message "Unable to fetch value for secret BCKUPKEY_13bb48fc-0844 > > -4736-9972-e26453333856, are we an

Hello, [ I've just reported this as https://bugzilla.samba.org/show_bug.cgi?id=2116 ] ------------------ rsync-2.6.3 can fail to report a write error. Here's a demonstration, writing to a full partition: You can reproduce it like this: $ echo foo > in $ strace -f -o log rsync in /full/tmp $ grep 'write.*ENOSP' log 4787 write(1, "foo\n", 4) =

Author: rmesta Repository: /hg/zfs-crypto/gate Revision: a5e1262c14c8b8b2e86d10d72c8edef705b390f5 Log message: 6346204 NFSv4 client suffers undetected write errors to full file system Files: update: usr/src/uts/common/fs/nfs/nfs4_vnops.c

Garming - thanks for your quick response. That link you gave me has Samba 3.x patches. I didn't notice any links to 4.x patches. Official Distro Releases are often behind the current stable release, generally. In fact, when I first installed Samba4 the Linux version was more recent than the Ubuntu version. This lag is probably due to abundance of caution and/or lack of manpower. I

I upgraded from 4.1.23 to 4.2.12 and am now getting (lots of) messages: Unable to fetch value for secret BCKUPKEY_, are we an undetected RODC? I found an almost identical message (titled: "Update samba4 from 4.1.17 to 4.2.1 failed") on the web from May 22, 2015 at: http://samba.2283325.n4.nabble.com/Update-samba4-from-4-1-17-to-4-2-1-failed-td4686215.html but saw no resolution other

Hi, I'm sure that you are all aware that the mount utilities that ship with samba are designed to compile and run only with Linux 2.1 series development kernels. I'll _try_ keep this short and sweet while doing my best to explain what I have done, since I have a tendancy to ramble on. I have two boxes, one Linux with libc5, and another with Linux and Glibc2 (aka libc6). The Samba

i_alloc_sem has always been a bit of an odd "lock". It''s the only remaining rw_semaphore that can be released by a different thread than the one that locked it, and it''s use case in the core direct I/O code is more like a counter given that the writers already have external serialization. This series removes it in favour of a simpler counter scheme, thus getting rid

Am 27.06.2000 19:58:44 schrieb urban: > On Tue, 27 Jun 2000 klaus-georg.adams@rwg.de wrote: > > > > > Hi Andrew, > > your patch from 2.2.15 to 2.2.16, backing out the older protocol levels breaks > > reading from an OS/2 LAN Server. > > The appended patch fixes things for me (against 2.2.16). > > This backs out a lot of desired changes. For example I think

Has anyone tried LFS (ie >2G files support) and Ext3 together? Are there good reasons why this should/should not work? I see the RH enterprise kernel patch set specifically does not attempt both lfs and ext3, but the lfs patches themselves touch some reasonably localised parts of ext2, so I would hope (without having dived in there to test), that the ext3 changes would mirror that

... Initializing.. hi all, I've a a very basic setup, directly two boxes via two MHEH28-XTC and I cannot activate them. One peculiar thing is I get (randomly & !often): [85947.090496] AMD-Vi: Event logged [ [85947.090539] IO_PAGE_FAULT device=09:00.7 domain=0x0000 address=0x00000000f6ffb000 flags=0x0050] [85947.298509] AMD-Vi: Event logged [ [85947.298550] IO_PAGE_FAULT device=09:00.7

Hi, These three patches fix the problems in the version two. And them base on the Tao's patches: ocfs2/xattr: xattr improvement The first patch fix some problem in xattr code. The second patch add security EA support. The third patch add ACL support. Best regards, tiger