Sorry it's been a bit since I reported back, but I got a chance to apply
your patch and I have mixed results to report. Basically, it looks like
the patch may resolve the issues, but not entirely.
After building the new kernel, I was still able to reproduce the problem
initially
I've made it through the initial build and the problem does in fact still
occur. I completed the build with CONFIG_AUFS_DEBUG=y and as one would
expect, the problem still occurs. Â Interestingly, I cannot reproduce 100%
of the time in the way previously described. Here is what
Michael Johnson - MJ:
I've made it through the initial build and the problem does in fact still
occur. I completed the build with CONFIG_AUFS_DEBUG=y and as one would
expect, the problem still occurs. Interestingly, I cannot reproduce 100%
of the time in the way previously described. Here
I will see if I can reproduce in a vm and generate very specific
instructions to reproduce. I think I will have time to do this later
today.
On Feb 1, 2015 10:37 PM, [1]sf...@users.sourceforge.net wrote:
[2]sf...@users.sourceforge.net:
I have tried but could not
Michael Johnson - MJ:
I will see if I can reproduce in a vm and generate very specific
instructions to reproduce. I think I will have time to do this later today.
Thank you very much.
Other testers are also welcome.
The first debug patch I will ask will be the one in
sf...@users.sourceforge.net:
I have tried but could not reproduce the problem.
- got full trusty kernel source, built it with the default configuration
(as MJ posted) -- no disk space
- disabled unnecessary drivers, built again -- succeeded
- rebooted with the new kernel, tried, but could
sf...@users.sourceforge.net:
Anyway I will try ubuntu kernel by myself, although it will take long
time...
I have tried but could not reproduce the problem.
- got full trusty kernel source, built it with the default configuration
(as MJ posted) -- no disk space
- disabled unnecessary
Dan Kegel:
root@ubu14-bb-01:/var/lib/lxc/ubu14-bb-01-ubu1204-temp-g-speak-unique/foobar#
mkdir -p dir1/dir2
root@ubu14-bb-01:/var/lib/lxc/ubu14-bb-01-ubu1204-temp-g-speak-unique/foobar#
rm -rf dir1
root@ubu14-bb-01:/var/lib/lxc/ubu14-bb-01-ubu1204-temp-g-speak-unique/foobar#
ls
ls: cannot
I see very similar behavior (and always have with AUFS) and it is easily
reproducible. Here is how to reproduce 100% of the time:
$ cd /aufsdir;
$ mkdir -p dir1/dir2;
$ rm -rf dir1
$ ls
ls: cannot open directory .: Stale file handle
To mke the error go away:
$ cd .
... although if it's bug #1, I'm not sure why it just showed up for me
with btrfs and not ext4...
On Tue, Jan 27, 2015 at 4:03 PM, Dan Kegel d...@kegel.com wrote:
Thanks for the short repro script.
This prevents debian packaging tools from working; seems like it'd be
good to fix it in aufs
Michael Johnson - MJ:
$ cd /aufsdir;
$ mkdir -p dir1/dir2;
$ rm -rf dir1
$ ls
ls: cannot open directory .: Stale file handle
At least, these steps succeeded on my test machine.
$ mkdir -p dir1/dir2
$ rm -ir dir1
rm: descend into directory `dir1'? y
rm: remove directory `dir1/dir2'? y
aufs
Dan Kegel:
I see that Ubuntu 14.04's using kernel 3.13.mumble, and aufs no longer
Is this your Ubuntu 14.04?
2d22fc7 2014-10-09 UBUNTU: Ubuntu-3.13.0-38.65
According to git://kernel.ubuntu.com/ubuntu/ubuntu-trusty.git, it uses
aufs3.13-20140303. As always, ubuntu uses old version
According to git://kernel.ubuntu.com/ubuntu/ubuntu-trusty.git, it uses
aufs3.13-20140303. As always, ubuntu uses old version enough to make it
very hard for me suppport. But I am trying, as always, to support and
help users.
Ah, I might be confused, sorry.
If ubuntu-trusty.git is release on
13 matches
Mail list logo
