Thank you very much for your very detailed response. This is the major
difference from the Unionfs mail-list, where there is often no
response.

The idea of temporarily remounting with 'udba=inotify' looks like a
great idea! I'll try it.

I will also try the patch to mount a Squashfs file that is present in
another branch.

This is great, thanks again for your responsiveness. Note, regarding
my previous attempt to explain one or more of these issues, that was a
long time ago, and I don't recall the details -- probably my
explanation back then was too vague.

Regarding f.s. corruption, it is another Puppy Linux developer
(Jemimah) who was having trouble. I did have a one-off problem but it
didn't repeat so I don't really know what that problem was. I'll do
another kernel compile (with the patch applied to Aufs) and will see
if I can get any f.s. errors.

One interesting point about the 2.6.33 kernel is that they have
dropped the ext2 and ext3 drivers as the new ext4 driver handles those
also. -- probably has nothing to do with this topic, just an
interesting item of news.

Regards,
Barry Kauler


On 3/23/10, sf...@users.sourceforge.net <sf...@users.sourceforge.net> wrote:
>
>> > First reason
>>      :::
>> > If we have a "save partition" on top, we also have the SFS files in
>> > that partition. Aufs will refuse to mount those SFS files as they are
>> > already inside a branch. Consequently, we are forced to copy the main
>> > SFS file into RAM and mount it from there. However, Unionfs is quite
>> > happy with mounting SFS files that are actually present in another
>> > branch.
>>
>> Because I had experienced a recursive lock (deadlock) by a loopback
>> branch (fs image in a branch fs), aufs rejects it.
>> But it was a long time ago. It was early stage in aufs1 era.
>> I will check it again with recent kernel.
>
> It may work.
> At least, my simple tests are passed.
> Here is a patch for you. Test it well, if you want.
>
>
> J. R. Okajima
>
>
> diff --git a/fs/aufs/loop.c b/fs/aufs/loop.c
> index 5fceec7..2a78a8d 100644
> --- a/fs/aufs/loop.c
> +++ b/fs/aufs/loop.c
> @@ -32,6 +32,7 @@ int au_test_loopback_overlap(struct super_block *sb,
> struct dentry *h_d1,
>       struct inode *h_inode;
>       struct loop_device *l;
>
> +     return 0;
>       h_inode = h_d1->d_inode;
>       if (MAJOR(h_inode->i_sb->s_dev) != LOOP_MAJOR)
>               return 0;
>

------------------------------------------------------------------------------
Download Intel&#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev

Reply via email to