Re: Fwd: aufs - Text file busy error

It is very nice to hear that this fix will be introduced to AuFS. Thank you for your time and help! On Fri, Feb 5, 2016 at 6:44 PM, <[1]sf...@users.sourceforge.net> wrote: Thanks for testing. James Burry: > I applied this patch, and it appears to be working. The build sof

Re: Fwd: aufs - Text file busy error

Thanks for testing. James Burry: > I applied this patch, and it appears to be working. The build software is > no longer reporting "text file busy". Do you think that this patch will > make it into the official AUFS tree ? Yes, it will. I will refine the patch and apply to every versions aufs3.1

Re: Fwd: aufs - Text file busy error

Thank you for explaining the patch. It is nice to know a bit more about aufs. I applied this patch, and it appears to be working. The build software is no longer reporting "text file busy". Do you think that this patch will make it into the official AUFS tree ? I will perform mor

Re: Fwd: aufs - Text file busy error

James Burry: > Here is the kernel message produced : Thanx for the call trace. Here is my current guess. Brief scenario - chmod sets "this file is being changed" mark to the file inode. - exec(./a.sh) checks the mark, and rejects as "the file should not be changed during the execution." Rather

Re: Fwd: aufs - Text file busy error

Here is the kernel message produced : [ 5185.703098] [ cut here ] [ 5185.703120] WARNING: CPU: 2 PID: 31077 at include/linux/fs.h:2502 au_h_open+0x209/0x250() [ 5185.703121] Modules linked in: binfmt_misc nls_utf8 isofs nfsv3 nfs_acl nfs lockd grace fs

Re: Fwd: aufs - Text file busy error

Hi JR. Yes, the RW branch is local ext2 on /dev/sdb1 I will try the patch and let you know what happens. I did verify that the culprit was not NFS. I copied all of the NFS files locally (to an ext2 filesystem) and the same error occurred (text file busy). On Thu, Feb 4, 2016 at 8:

Re: Fwd: aufs - Text file busy error

James Burry: > All of the ro branches are mounted from an NFS share. Maybe the extra > latency associated with the NFS share has something to do with the issue. > The file which is causing the "text file busy" error for me is coming form > /proj/5.113.79.8/.isoMounts/114_ThirdPartyLinuxDev.iso=ro,

Re: Fwd: aufs - Text file busy error

James Burry: > The .rw branch (/proj/5.113.79.8/.scratch ) is > ext2. http?? Let me make sure once again. Your RW branch is local ext2 as /dev/sda1, right? J. R. Okajima -- Site24x7 APM I

Re: Fwd: aufs - Text file busy error

The .rw branch (/proj/[1]5.113.79.8/.scratch) is ext2. On Thu, Feb 4, 2016 at 9:30 AM, <[2]sf...@users.sourceforge.net> wrote: James Burry: > root@U1204-32-BS:~# cat /sys/fs/aufs/si_3532123f/br* > /proj/[3]5.113.79.8/.scratch=rw     ::: > /proj/[4]5.113.79

Re: Fwd: aufs - Text file busy error

James Burry: > root@U1204-32-BS:~# cat /sys/fs/aufs/si_3532123f/br* > /proj/5.113.79.8/.scratch=rw ::: > /proj/5.113.79.8/.isoMounts/114_ThirdPartyLinuxDev.iso=ro ::: > All of the ro branches are mounted from an NFS share. Maybe the extra > latency associated with the NFS share ha

Re: Fwd: aufs - Text file busy error

Thank you for looking into this. My branches - root@U1204-32-BS:~# cat /sys/fs/aufs/si_3532123f/br* /proj/[1]5.113.79.8/.scratch=rw /proj/[2]5.113.79.8/.isoMounts/1790_SGF_Game_TreasuresOfOlympus_V2LinuxDev.i so=ro /proj/[3]5.113.79.8/.isoMounts/OS.NVIDIA-GF8.FIELD.2.0.168.0.i

Re: Fwd: aufs - Text file busy error

James Burry: > I tried the aufs-4.4 Linux tree from git ( > git://github.com/sfjro/aufs4-linux.git > ) > > I still see these "text file busy" errors. The errors happen in a chroot > environment of the aufs mountpoint. I've tried aufs4.4 too, and succeeded

Re: Fwd: aufs - Text file busy error

I tried the aufs-4.4 Linux tree from git ([1]git://github.com/sfjro/aufs4-linux.git) I still see these "text file busy" errors. The errors happen in a chroot environment of the aufs mountpoint. I have verified that the errors do not occur in Ubuntu 12.04 (kernel 3.2.0). Do you

Re: Fwd: aufs - Text file busy error

Hello James, James Burry: > Hello everyone. I am attempting to use aufs with Ubuntu 14.04.3. When I run > the line below in an aufs filesystem, I will intermittently get an error - > "text file is busy" > > chmod +x script.sh && ./script.sh I didn't know such problem. Your kernel, Ubuntu 14.04.3

Fwd: aufs - Text file busy error

Hello everyone. I am attempting to use aufs with Ubuntu 14.04.3. When I run the line below in an aufs filesystem, I will intermittently get an error - "text file is busy" chmod +x script.sh && ./script.sh Others have reported a similar issue here - [1]https://github.com/docker/dock