Page 2 of 6 FirstFirst 1234 ... LastLast
Results 11 to 20 of 51

Thread: fusecompress on knoppix-data.img?

  1. #11
    Senior Member registered user
    Join Date
    Dec 2009
    Posts
    423
    Quote Originally Posted by dinosoep View Post
    I am currently trying to compile the newest version without succes, I'll continue my quest tomorrow
    Instead of compiling, have you tried just install aufs-tools from synaptics ?

    What is the error when you try to compile it ?
    Do you have /usr/include/linux/aufs_type.h on your system ?

  2. #12
    Senior Member registered user
    Join Date
    Sep 2006
    Posts
    802

    Why are special tools needed here?

    I just wonder why special tools should be needed if the semantics in aufs2 is as advertised? If knoppix-data.img and ramdisk are both mounted read-write, shouldn't it be possible just to rsync ramdisk onto knoppix-data.img?

    BTW, I have another use for aufs: When using databases and web servers, we may use a lot of space, not easily accomodated on the persistent image, but standard package installation will place them there nonetheless. Instead of changing installation data, or introduce symlinks, we could simply move data to persistent image versions, and union mount those with larger store versions. We could then union merge the versions, and, eventually, create dummy stores for use when larger stores are not mounted. I think of something like:

    Code:
    mount -t aufs -o dirs=/var/lib/mysql_ps:/store/var/lib/mysql none /var/lib/mysql
    mount -t aufs -o dirs=/var/www_ps:/store/var/www none /var/www

  3. #13
    Senior Member registered user
    Join Date
    Sep 2006
    Posts
    802

    Debian aufs - a sad state of affairs?

    In the sourceforge mailing list for aufs, the main developer recently posted the following:
    http://sourceforge.net/mailarchive/f...ame=aufs-users

    And more importantly, the aufs module in debian is totally broken. Last
    time I saw aufs in debian, they use TOO OLD version which is obsoleted
    and not maintained. Additionally they made their original changes. It
    means I cannot support aufs in debian.
    Maybe the safest thing is to get the source off sourceforge and proceed?

  4. #14
    Senior Member registered user
    Join Date
    May 2006
    Location
    Columbia, Maryland USA
    Posts
    1,631
    @ Capricorny

    I think you should post this on the debian-knoppix list,
    with attn to Klaus Knopper. Sounds serious.

    http://lists.debian.org/debian-knoppix/2011/06/

  5. #15
    Senior Member registered user
    Join Date
    Dec 2009
    Posts
    423
    Quote Originally Posted by Capricorny View Post
    Maybe the safest thing is to get the source off sourceforge and proceed?
    If you are talking about aufs kernel module for KNOPPIX, there is nothing to worry, Klaus K would have compiled the right version for it. If it had been the wrong version, it wouldn't compile with newer kernel and it won't run. It would be noticed !

    By contrast the debian version might be old and faulty, because a typical debian user won't use aufs, so even if it is old and faulty, it would go unnoticed.

    If you are talking about aufs-utils or aufs-tools, then I can't say anything about the debian version, because in a typical use, the aufs-utils are not used at all. It would not be surprising if the package faulty.

  6. #16
    Senior Member registered user
    Join Date
    Dec 2009
    Posts
    423
    Quote Originally Posted by Capricorny View Post
    I just wonder why special tools should be needed if the semantics in aufs2 is as advertised? If knoppix-data.img and ramdisk are both mounted read-write, shouldn't it be possible just to rsync ramdisk onto knoppix-data.img?
    Aufs is more than just adding new files and modifying existing files. It is also able to "delete" or "hide" an existing files or directory. There is certain encoding or protocol to fully represent the modified file system structure. And therefore it is better to use the tools provided than to re-invent the wheel.

  7. #17
    Senior Member registered user
    Join Date
    Sep 2006
    Posts
    802

    More yes, but how much is needed here?

    Quote Originally Posted by kl522 View Post
    Aufs is more than just adding new files and modifying existing files. It is also able to "delete" or "hide" an existing files or directory. There is certain encoding or protocol to fully represent the modified file system structure. And therefore it is better to use the tools provided than to re-invent the wheel.
    If you have to modify the whole structure, definitely yes. But is that really necessary for this particular use?

    If we do something like

    Code:
    mount -t aufs -o dir=ramdisk=rw:persistent_image=rw:KNOPPIX=ro none /unionfs
    What would go wrong if we did (evt. as a cron job)

    Code:
    rsync -ax ramdisk/ persistent_image
    I just tested this with a couple of directories with a few files. Seemed to work in that case, at least.

  8. #18
    Senior Member
    Join Date
    Jan 2011
    Posts
    123
    @kl522 the script I use needs to have aufs-utils the same version as the aufs patch-version, when I tried with the one from synaptic it gave me:
    Code:
    "aubrsync move_with_wh /UNIONFS /KNOPPIX-DATA-RAMDISK /KNOPPIX-DATA"
    and that gives me the following errors:
    + mount -o remount,ro,udba=reval,noshwh /UNIONFS
    /sbin/mount.aufs:plink.c:223: AUFS_CTL_PLINK_MAINT: Inappropriate ioctl for device
    + mount -o remount,udba=reval,noshwh,rw,relatime,si=aa3aa37c,noplink /UNIONFS
    /sbin/mount.aufs:plink.c:223: AUFS_CTL_PLINK_MAINT: Inappropriate ioctl for device
    when I tried compiling from source it gave me:
    Code:
    install -d /usr/share/man/man5
    install -o root -g root -p -m 644 aufs.5 /usr/share/man/man5
    install -d /sbin
    install -o root -g root -p -m 755 mount.aufs umount.aufs auplink /sbin
    install: cannot stat `umount.aufs': No such file or directory
    make: *** [install_sbin] Error 1
    The maintainer suggested updating the kernel module which I'm going to try this evening


    @Capricorny
    The problem with rsync here is that when you delete a file, it should create a whiteout on the writeable upper filesystem and rsync doesn't sync those, only the real files get synced. (thats at least what I think, why else would they've created aubrsync?)

  9. #19
    Senior Member registered user
    Join Date
    Sep 2006
    Posts
    802
    Quote Originally Posted by dinosoep View Post
    The problem with rsync here is that when you delete a file, it should create a whiteout on the writeable upper filesystem and rsync doesn't sync those, only the real files get synced. (thats at least what I think, why else would they've created aubrsync?)
    Exactly. And I would ask: Why would they have to use aubrsync? My (implicit) point was that file creatons and updates are taken care of through rsync, while deletions must be done directly on the persistent image, preferably upon shutdown. Of course, it would be nice to have a "commit" function doing the actual deletions, determined from the ramdisk-recorded changes (whiteouts), but I will rather have something simple, stupid and robust than something that nobody seems to be able to tell how and why works or not.

  10. #20
    Senior Member
    Join Date
    Jan 2011
    Posts
    123
    I have no idea how I could make that and aubrsync sounds like a working solution.
    I have not the smallest idea on how I can update the aufs module in my kernel to the latest version without recompiling everything. or compile anything for that mather from aufs git without getting errors I'm hoping someone who does understand a bit about that would help me out

    for the intersted persons, here is the "nowear" initrd.gz
    Everyone can try their own scripts and see if they get the sync working
    http://dl.dropbox.com/u/15024434/initrd_nowear.gz

Page 2 of 6 FirstFirst 1234 ... LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  


HP ProLiant MicroServer Gen8 Server Xeon E3-1220L 16GB RAM No HDD's picture

HP ProLiant MicroServer Gen8 Server Xeon E3-1220L 16GB RAM No HDD's

$299.00



HP Proliant MicroServer Gen 8 2.3GHz CPU 16GB RAM NO DRIVES/CADDIES INCLUDED picture

HP Proliant MicroServer Gen 8 2.3GHz CPU 16GB RAM NO DRIVES/CADDIES INCLUDED

$179.99



HP ProLiant HSTNS-5151 Micro Server 8GB RAM No Drives/Key/Caddies *READ* picture

HP ProLiant HSTNS-5151 Micro Server 8GB RAM No Drives/Key/Caddies *READ*

$94.99



HP ProLiant MicroServer Gen8 Server Xeon E3-1220L 8GB RAM No HDD's picture

HP ProLiant MicroServer Gen8 Server Xeon E3-1220L 8GB RAM No HDD's

$229.99



HPE ProLiant MicroServer Gen 10 Plus, Xeon E-2224, 16GB DDR4, 1TB M.2 NVMe SSD picture

HPE ProLiant MicroServer Gen 10 Plus, Xeon E-2224, 16GB DDR4, 1TB M.2 NVMe SSD

$750.00



ProLiant MicroServer Gen8 Intel Xeon E3-1220L V2 2.3GHz CPU 8GB RAM picture

ProLiant MicroServer Gen8 Intel Xeon E3-1220L V2 2.3GHz CPU 8GB RAM

$170.00



HP ProLiant MicroServer Gen8 Server Intel Xeon E3-1220L v2 16GB DDR3 (4) 4TB HDs picture

HP ProLiant MicroServer Gen8 Server Intel Xeon E3-1220L v2 16GB DDR3 (4) 4TB HDs

$399.00



HP ProLiant N36L Micro Server 633724-001 AMD Athlon II Neo N36L - No HDDs picture

HP ProLiant N36L Micro Server 633724-001 AMD Athlon II Neo N36L - No HDDs

$102.59



HP ProLiant Microserver Micro Server HSTNS-5151 untested picture

HP ProLiant Microserver Micro Server HSTNS-5151 untested

$75.00



HPE ProLiant MicroServer Gen10 Plus v2 Ultra Micro Tower Server P54644001 picture

HPE ProLiant MicroServer Gen10 Plus v2 Ultra Micro Tower Server P54644001

$849.99