Re: [RFC] move-down
Feature sounds interesting. I see. That was very similar to what I was thinking. - by default, without specifying source/target branches, src is the first branch where the file exist and dst is the next lower writable branch. in this case, of course, the consistency is checked. - when a user specifies the source/target branches, aufs doesn't check the consistency. Reading your first mail, I was going to stop implementing the options to specify the src/dst branches. It was in order to keep the consistency. But I am chaging my mind again, and thinking about another new option nocheck. alternatives: rm has option prompt before every removal and mv has --interactive maybe something similar or other option could be --safe-mode (opposite of default nocheck) - without nocheck (default), aufs checks the consistency even if the src/dst are specified. - specifying nocheck explicitly, aufs skips the check. this option is just for the users who know what he is doing. Hmm, probably I need to review the design again. -- Regards. V.Krishn -- This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev
Re: GIT repo (Re: aufs3 GIT release)
On Friday, April 26, 2013 09:33:22 AM sf...@users.sourceforge.net wrote: sf...@users.sourceforge.net: The web interface of aufs GIT repos are still broken and the SourceForge engineering team is working on it. The GIT repo itself should be available and ok. Recently there happened several things on aufs GIT repos, both of my local and the public one on SF. And I made changes on very essential features of aufs at the same time. Hmm, I am afraid if I made a mistake in my git work (or in SF side), something unpleasant may happen. About the current situation of the public GIT repositories on SourceForge, as far as I know, - some branches are lost - some new commits (which were git-pushed at the same time with the lost branches) are kept - the repositories looks unreliable - the web interface is still broken I have sf aufs git clone dated 20130406. aufs-util-20130406.tar.bz2 (130kb) + aufs3-standalone-20130406.tar.bz2 (984kb) I am not sure if they are as should be. Pls let me know if they can be useful. For aufs like tool, I would suggest a github mirror. -- Regards. V.Krishn Very unpleasant. Additionally my local GIT repositories seems to be corrupted. - all refs (branches) are lost - most of old commits are kept - some new commits are lost I restored many of them from my backup. But some are totally gone, particulary my local working branches, which include some incomplete implementations and git-stash-es. I have tried git-push some lost new branches, but the SF GIT server behaves strangely and I am asking SF people. Since I am hoping the SF engineering team will recover well, if you find something wrong in your aufs GIT repository, please don't panic (like me). J. R. Okajima --- --- Try New Relic Now We'll Send You this Cool Shirt New Relic is the only SaaS-based application performance monitoring service that delivers powerful full stack analytics. Optimize and monitor your browser, app, servers with just a few lines of code. Try New Relic and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr -- Try New Relic Now We'll Send You this Cool Shirt New Relic is the only SaaS-based application performance monitoring service that delivers powerful full stack analytics. Optimize and monitor your browser, app, servers with just a few lines of code. Try New Relic and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr
Re: GIT repo (Re: aufs3 GIT release)
On Friday, April 26, 2013 08:45:46 PM you wrote: V.Krishn: I have sf aufs git clone dated 20130406. aufs-util-20130406.tar.bz2 (130kb) + aufs3-standalone-20130406.tar.bz2 (984kb) I am not sure if they are as should be. Pls let me know if they can be useful. For aufs like tool, I would suggest a github mirror. Thanks for your offer. But I could restored most of old objects (probably all). The totally lost objects are all non-public ones. By the way, I implemented the undeletable branch top dir we discussed while ago. This new branch attribute is set by default, and a user can disable/enable it manually. Thanks. Hope the default behaviour is accepted. Also if easily possible to maintain, can there be an official mirror at github or any other free repository. Searching github did show some unofficial mirror for aufs. -- Regards. V.Krishn -- Try New Relic Now We'll Send You this Cool Shirt New Relic is the only SaaS-based application performance monitoring service that delivers powerful full stack analytics. Optimize and monitor your browser, app, servers with just a few lines of code. Try New Relic and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr
Error - Stale NFS file handle
Did the following to set an aufs. cd /tmp mkdir branch ro u mount test.iso ro -o loop mount -t aufs -o br:branch:ro none u Now branch got accidently deleted and I am unable to unmount u nor ro Tried: umount -f u or umount -f ro Keep getting following error: umount2: Stale NFS file handle umount: u/: Stale NFS file handle I am using Knoppix 7.0.1. Any help would be great. -- Regards. V.Krishn -- Minimize network downtime and maximize team effectiveness. Reduce network management and security costs.Learn how to hire the most talented Cisco Certified professionals. Visit the Employer Resources Portal http://www.cisco.com/web/learning/employer_resources/index.html
Stale NFS file handle
Did the following to set an aufs. cd /tmp mkdir branch ro u mount test.iso ro -o loop mount -t aufs -o br:branch:ro none u Now branch got accidently deleted and I am unable to unmount u nor ro Tried: umount -f u or umount -f ro Keep getting following error: umount2: Stale NFS file handle umount: u/: Stale NFS file handle I am using Knoppix 7.0.1. Any help would be great. -- Regards. V.Krishn -- Minimize network downtime and maximize team effectiveness. Reduce network management and security costs.Learn how to hire the most talented Cisco Certified professionals. Visit the Employer Resources Portal http://www.cisco.com/web/learning/employer_resources/index.html
Re: Error - Stale NFS file handle
On Saturday, April 06, 2013 02:27:54 PM you wrote:
Hello V.Krishn,
V.Krishn:
umount -f u
or
umount -f ro
Keep getting following error:
umount2: Stale NFS file handle
umount: u/: Stale NFS file handle
I am using Knoppix 7.0.1.
Unforunately I am not a Knoppix user. What is your kernel version and
Linux Microknoppix 3.3.7-64 #40 SMP PREEMPT Tue May 22 08:47:38 CEST 2012
x86_64 GNU/Linux
aufs version?
How to get this?
And what is the filesystem of your /tmp?
tmpfs
but now have tried on ext3 also with same result.
Did you install aufs-util which contains /sbin/umount.aufs?
yes, did aufs-tools_3.0+20120411-2_i386.deb
auplink ./u flush
gives error:
auplink:auplink.c:60: chdir: Stale NFS file handle
If you can run strace umount u, then show me its output please.
execve(//bin/umount, [umount, u], [/* 22 vars */]) = 0
brk(0) = 0x805b000
access(/etc/ld.so.nohwcap, F_OK) = -1 ENOENT (No such file or
directory)
mmap2(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0xf7776000
access(/etc/ld.so.preload, R_OK) = -1 ENOENT (No such file or
directory)
open(/etc/ld.so.cache, O_RDONLY) = 3
fstat64(3, {st_mode=S_IFREG|0644, st_size=144282, ...}) = 0
mmap2(NULL, 144282, PROT_READ, MAP_PRIVATE, 3, 0) = 0xf7752000
close(3)= 0
access(/etc/ld.so.nohwcap, F_OK) = -1 ENOENT (No such file or
directory)
open(/lib/i386-linux-gnu/libblkid.so.1, O_RDONLY) = 3
read(3, \177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0PD\0\0004\0\0\0...,
512) = 512
fstat64(3, {st_mode=S_IFREG|0644, st_size=162240, ...}) = 0
mmap2(NULL, 165004, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) =
0xf7729000
mmap2(0xf774f000, 12288, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|
MAP_DENYWRITE, 3, 0x25) = 0xf774f000
close(3)= 0
access(/etc/ld.so.nohwcap, F_OK) = -1 ENOENT (No such file or
directory)
open(/lib/i386-linux-gnu/libmount.so.1, O_RDONLY) = 3
read(3,
\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\200Y\0\0004\0\0\0..., 512) =
512
fstat64(3, {st_mode=S_IFREG|0644, st_size=166236, ...}) = 0
mmap2(NULL, 164880, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) =
0xf770
mmap2(0xf7727000, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|
MAP_DENYWRITE, 3, 0x27) = 0xf7727000
close(3)= 0
access(/etc/ld.so.nohwcap, F_OK) = -1 ENOENT (No such file or
directory)
open(/lib/i386-linux-gnu/libc.so.6, O_RDONLY) = 3
read(3, \177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0po\1\0004\0\0\0...,
512) = 512
fstat64(3, {st_mode=S_IFREG|0755, st_size=1331336, ...}) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0xf76ff000
mmap2(NULL, 1345848, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) =
0xf75b6000
mprotect(0xf76f8000, 4096, PROT_NONE) = 0
mmap2(0xf76f9000, 12288, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|
MAP_DENYWRITE, 3, 0x142) = 0xf76f9000
mmap2(0xf76fc000, 10552, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|
MAP_ANONYMOUS, -1, 0) = 0xf76fc000
close(3)= 0
access(/etc/ld.so.nohwcap, F_OK) = -1 ENOENT (No such file or
directory)
open(/lib/i386-linux-gnu/libuuid.so.1, O_RDONLY) = 3
read(3,
\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\260\22\0\0004\0\0\0..., 512)
= 512
fstat64(3, {st_mode=S_IFREG|0644, st_size=18000, ...}) = 0
mmap2(NULL, 20712, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) =
0xf75b
mmap2(0xf75b4000, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|
MAP_DENYWRITE, 3, 0x3) = 0xf75b4000
close(3)= 0
access(/etc/ld.so.nohwcap, F_OK) = -1 ENOENT (No such file or
directory)
open(/lib/i386-linux-gnu/libselinux.so.1, O_RDONLY) = 3
read(3,
\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\360O\0\0004\0\0\0..., 512) =
512
fstat64(3, {st_mode=S_IFREG|0644, st_size=124996, ...}) = 0
mmap2(NULL, 130140, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) =
0xf759
mmap2(0xf75ae000, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|
MAP_DENYWRITE, 3, 0x1d) = 0xf75ae000
close(3)= 0
access(/etc/ld.so.nohwcap, F_OK) = -1 ENOENT (No such file or
directory)
open(/lib/i386-linux-gnu/libsepol.so.1, O_RDONLY) = 3
read(3,
\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\0208\0\0004\0\0\0..., 512) =
512
fstat64(3, {st_mode=S_IFREG|0644, st_size=268512, ...}) = 0
mmap2(NULL, 272736, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) =
0xf754d000
mmap2(0xf758e000, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|
MAP_DENYWRITE, 3, 0x40) = 0xf758e000
close(3)= 0
access(/etc/ld.so.nohwcap, F_OK) = -1 ENOENT (No such file or
directory)
open(/lib/i386-linux-gnu/libdl.so.2, O_RDONLY) = 3
read(3, \177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0`\n\0\0004\0\0\0...,
512) = 512
fstat64(3, {st_mode=S_IFREG|0644, st_size=9844
Re: Error - Stale NFS file handle
On Saturday, April 06, 2013 02:27:54 PM you wrote: Hello V.Krishn, V.Krishn: umount -f u or umount -f ro Keep getting following error: umount2: Stale NFS file handle umount: u/: Stale NFS file handle I am using Knoppix 7.0.1. Unforunately I am not a Knoppix user. What is your kernel version and aufs version? #define AUFS_VERSION3.2-20120312 from /usr/include/linux/aufs_type.h -- Regards. V.Krishn -- Minimize network downtime and maximize team effectiveness. Reduce network management and security costs.Learn how to hire the most talented Cisco Certified professionals. Visit the Employer Resources Portal http://www.cisco.com/web/learning/employer_resources/index.html
Re: Stale NFS file handle
On Saturday, April 06, 2013 05:53:33 PM you wrote: umount -f -l ro is the closest you will get. The entry will be removed from the mount table and the actual unmount will happen when it can (never) but at least you needn't worry about it. Thanks, this does seems to solve the ro dir (still to check if it frees the .iso file) u dir is still the same. ls show the following: d? ? ? ? ?? u I tried simulating the issue on another distro with same result (just to be sure that this is not a Knoppix issue). -- Regards. V.Krishn On 4/6/13, V.Krishn vkris...@gmail.com wrote: Did the following to set an aufs. cd /tmp mkdir branch ro u mount test.iso ro -o loop mount -t aufs -o br:branch:ro none u Now branch got accidently deleted and I am unable to unmount u nor ro Tried: umount -f u or umount -f ro Keep getting following error: umount2: Stale NFS file handle umount: u/: Stale NFS file handle I am using Knoppix 7.0.1. Any help would be great. -- Regards. V.Krishn - - Minimize network downtime and maximize team effectiveness. Reduce network management and security costs.Learn how to hire the most talented Cisco Certified professionals. Visit the Employer Resources Portal http://www.cisco.com/web/learning/employer_resources/index.html -- Minimize network downtime and maximize team effectiveness. Reduce network management and security costs.Learn how to hire the most talented Cisco Certified professionals. Visit the Employer Resources Portal http://www.cisco.com/web/learning/employer_resources/index.html
Re: Error - Stale NFS file handle
On Saturday, April 06, 2013 06:23:11 PM you wrote: V.Krishn: Linux Microknoppix 3.3.7-64 #40 SMP PREEMPT Tue May 22 08:47:38 CEST 2012 x86_64 GNU/Linux aufs version? How to get this? It is printed when you load aufs. See your kernel log. In another mail, you wrote #define AUFS_VERSION3.2-20120312 but I'd like to make sure via kernel log. dmesg|grep aufs aufs 3.3-20120420 If you can run strace umount u, then show me its output please. execve(//bin/umount, [umount, u], [/* 22 vars */]) = 0 readlink(/tmp/u, 0xfff9de59, 4096)= -1 ESTALE (Stale NFS file handle) In your strace output, readlink(2) returns ESTALE very early before actual umount(2). I am afraid no one can touch your /tmp/u already. When and how such situation began? What did you do? Something like umount -l u? I generally use just umount and sometimes -f option. Simulated the issue in kvm -m 256 -cdrom /media/sdd1/iso/systemrescuecd-x86-2.8.1.iso to get the same result. Steps. 1. cd /tmp 2. mkdir branch ro u 3. mkisofs -o temp.iso somefiles 4. mount temp.iso ro other steps then deleted branch same problem from here... I know modifying branch dir directly is not recommended, I was unable to unmount the locked .iso file which became an issue. -- Regards. V.Krishn -- Minimize network downtime and maximize team effectiveness. Reduce network management and security costs.Learn how to hire the most talented Cisco Certified professionals. Visit the Employer Resources Portal http://www.cisco.com/web/learning/employer_resources/index.html
