Benchmarking Filesystems Part ||

Hi,
Probably most of you here read Slashdot and probably everyone have already read this benchmark article. For those who didn't:
Benchmarking Filesystems Part II, by Justin Piszcz
It looks really suprising. It appears that ReiserV4, which all seem to be so fond of, isn't the best idea for low-CPU machines or laptops (where CPU usage=power). I wouldn't be really suprised if it's benchmarks wouldn't shine on fast machines either.
I'm currently running ReiserV3 (and, as pointed out in the benchmark, it's mounttimes suck), but after reading this article I think of moving FSs. Ext3 seems to have gotten a lot better since last benchmark - too bad dir_indexing wasn't benchmarked. I've never really checked out XFS or JFS, but judging from the article these look really promising. Anyone tried these?
Thoughts/comments/overall discussion follows...

Here are my findings. Again, between hardware and users' needs, YMMV. My results for XFS, for example, probably won't apply to you if you have a fast SATA or SCSI drive, and you'll find ext3 grossly lacking if you're dealing with filesystems of petabyte size (e.g. systems that handle data from particle colliders).
- JFS is fast, CPU efficient, and generally rocks. It's not quite as good with lots of small files as ReiserFS, but very close, and appears to have faster read speeds.
- Indexed ext3 is very very very fast for just about everything... except pacman. It seems, for some reason, that the pacman "database" gets fragmented a bit faster on ext3 than on other filesystems. The slight sluggishness of pacman isn't a showstopper though, and pacman-optimize usually takes care of it for a while. Other than that, though, indexed ext3 is very good.
- Non-indexed ext3 is very slow. My general recommendation is to never use ext3 without directory indexing.
- ReiserFS is pretty good. There's supposedly a performance hit from tail packing, but I've never seen increased performance with tail packing turned off. I do have a major complaint about it though: journal replay on mount, which takes forever for large volumes.
- XFS is incredibly slow, and causes a lot of hard drive grinding, especially when dealing with lots of small files - although for me, it doesn't perform well with large ones either. I've heard tell of ways to make it perform better with small files, but never found details on them, and I'm betting they're quite mythical; at any rate, I don't think it would make a difference, as this filesystem seems to disagree with my HDDs.
- Ext2 (nonjournalled) should NEVER be used on hard drives. I learned this in a rather irritating way, when my ext2 boot partition became corrupted when I accidentally hit the power switch while my machine was still on, and a kernel panic message greeted me on the next boot. There's a good reason to use journalled filesystems, folks!

Similar Messages

  • Hard drive benchmarking.

    Hi,
    I have two hard drives, one of which I'd like to use for Arch (/, /boot, /home, ...), so I'm trying to figure out which one would be best suited for the task.
    I have the following questions :
    -Are these commands an accurate way of ranking them:
    dd if=/dev/zero of=tempfile bs=1M count=1024 conv=fdatasync,notrunc
    echo 3 > /proc/sys/vm/drop_caches
    dd if=tempfile of=/dev/null bs=1M count=1024
    -Does the fact that one of the disks is mounted as / significantly alter the results ?
    -Is the LVM overhead measurable ?
    -The rudimentary results I obtained show that one disk is better than reading while the other at writing (R-W : 70MB/s - 57MB/s, R-W : 108MB/s - 38MB/s) ; my intuition tells me that for a root partition, the reading speed matters more than writing, is this correct ? At what "ratio" or absolute value does this stop being the case ? Other factors (e.g. for a system with high swap usage, writing speed should matter more) ?
    Feel free to offer links or additional information.
    Thank you for reading, and potentially helping (me, and other readers from the future).
    Last edited by Resistance (2015-03-11 13:37:18)

    Resistance wrote:
    Hi,
    I have the following questions :
    -Are these commands an accurate way of ranking them:
    dd if=/dev/zero of=tempfile bs=1M count=1024 conv=fdatasync,notrunc
    echo 3 > /proc/sys/vm/drop_caches
    dd if=tempfile of=/dev/null bs=1M count=1024
    In short, no. Not by a long shot. In order to do precise measurement you'd have to go beyond volume management, let alone the filesystem.
    -Does the fact that one of the disks is mounted as / significantly alter the results ?
    Most likely yes. Depends on how the box is used during the test.
    -Is the LVM overhead measurable ?
    No. The testing should be done under LVM, e.g. on the block layer, or even lower (ATA) as long as you're interested in hardware-related numbers and not benchmarking filesystems. But even low-level test results are questionable, see below.
    -The rudimentary results I obtained show that one disk is better than reading while the other at writing (R-W : 70MB/s - 57MB/s, R-W : 108MB/s - 38MB/s) ; my intuition tells me that for a root partition, the reading speed matters more than writing, is this correct ? At what "ratio" or absolute value does this stop being the case ? Other factors (e.g. for a system with high swap usage, writing speed should matter more) ?
    These results can be biased heavily depending on testing conditions. If you want to measure hard drive's performance, go for more low-level tools. And even when you finish the tests, the results won't tell you which drive will behave better under regular working conditions. Many performance factors are dependent on software, being it the controller firmware, the hard drive firmware or the operating system. Unless the two drives have big differences on the hardware level (like, say, higher RPM, larger cache, etc.), it doesn't make much sense benchmarking them against each other.
    Go for reliability, not performance. Run some SMART tests, badblocks, etc. and then choose the worse drive for OS and the better one for data.

  • How to dual boot with Windows 8.1 and Arch?

    Hello everyone,
    I've been looking into using Linux as my daily driver since having some experience with it on a server. After some digging around, I think Arch Linux is the best distro for me, now onto where I am.
    I'm currently running Windows 8.1 (updated from Windows 8, which updated from Windows 7) on a Dell Inspiron 15R SE laptop, I want to dual boot Arch Linux with it. I've looked at the wiki and I'm still not entirely sure what to do.
    Can anyone give me a quick list of steps of what to do to dual boot this? I've dual booted Ubuntu in the past and it was really simple because an installer did it all.
    Thanks, Expi.

    stqn wrote:
    Expi1 wrote:Thanks, I'm mostly struggling with how to partition for Arch and then how to do the bootloader. I'm using Win8 64-bit and from what I understand a Legacy BIOS bootloader. I'm not entirely sure what I should be partitioning the C: into, I've done partitions before, just not for Arch and then I'm not sure whether to use GRUB or syslinux, or if I even need those. Or if I need to use GPT or MBR?
    Your disk is already partitionned so you don’t have to choose between GPT or MBR, the choice is already made.
    You don’t partition “C:”, that is the name of a Windows partition. You partition a drive.
    Grub or syslinux, use whatever the beginners guide tells you to. Personally I think syslinux is simpler which is why I’m using it (but I’m not dual-booting, if that matters).
    You’re not saying what your problem is with partitionning, so it’s hard to help.
    Thanks for getting back to me, I'm not sure if I just create one large partition for Archlinux or if I have to create multiple? Where I'm also confused is with the Creating Filesystems part of the guide. I don't understand how I'd do this in Windows, or what /dev/sda1 is referring to.
    As for the bootloader part, the Beginner's Guide gives you a choice between syslinux and grub, what I'm not sure about is which to use considering I'm dualbooting. How it will affect my windows bootloader, do I disregard that and use GRUB now? I'm unclear on how that works.
    I'm also aware I need to disable Secure Boot, I just searched my BIOS options and couldn't find anything remotely relating to that, so I'm assuming it's not an issue since this computer was originally on Windows 7 anyway?
    Thanks again, Expi.
    Last edited by Expi1 (2014-03-06 19:54:30)

  • Partition an Advanced Format drive with 4KB sector (for Linux OS only)

    I got a brand new WD 1TB drive, model WD10EZEX, I'm upgrading from an old 500 GB drive with Arch running on it, and I'm going to make a fresh Arch install on it.
    I suddenly learned about all this Advanced Format issue, with the first units "lying" about physical sector size and all that stuff, which started like 2 years ago and I was not aware of.
    I couldn't find a step by step guide to perform the proper formatting for a fresh Linux OS install with 4KB-sector, despite the info is out there scattered in tons of blogs, forums, etc.
    I figured out the steps for my simple setup, and I'd like to know if everything is all right. For the ones who already know the steps, can you please go to the bottom of the post, and tell me if the final setup is all right to start the fresh install ??  I reproduce all the steps hoping that this will help other people in the future.
    I'll use the whole drive only for an Archlinux install, with one partition for the / and another for /home.
    Seems the GPT modern method is the way to go, and the gdisk tool will do the trick. If we are booting from this drive, with GRUB2 in a BIOS system, we must also create a BIOS Boot Partition.
    So, with the drive having no partitions at all, and sda being the device name
    # gdisk /dev/sda
    Command (? for help): p
    Disk /dev/sda: 1953525168 sectors, 931.5 GiB
    Logical sector size: 512 bytes
    Disk identifier (GUID): 6527769B-B4BC-408C-A45B-D2DAA4036620
    Partition table holds up to 128 entries
    First usable sector is 34, last usable sector is 1953525134
    Partitions will be aligned on 2048-sector boundaries
    Total free space is 1953525101 sectors (931.5 GiB)
    Number Start (sector) End (sector) Size Code Name
    we create the 2 MiB BIOS Boot Partition
    Command (? for help): n
    Partition number (1-128, default 1): 1
    First sector (34-1953525134, default = 2048) or {+-}size{KMGTP}: 2048
    Last sector (2048-1953525134, default = 1953525134) or {+-}size{KMGTP}: +2M
    Current type is 'Linux filesystem'
    Hex code or GUID (L to show codes, Enter = 8300): ef02
    a 45GB partition to use as /
    Command (? for help): n
    Partition number (2-128, default 2):
    First sector (34-1953525134, default = 6144) or {+-}size{KMGTP}:
    Last sector (6144-1953525134, default = 1953525134) or {+-}size{KMGTP}: +45G
    Current type is 'Linux filesystem'
    Hex code or GUID (L to show codes, Enter = 8300): 8300
    Changed type of partition to 'Linux filesystem'
    and the rest to use as /home
    Command (? for help): n
    Partition number (3-128, default 3): 3
    First sector (34-1953525134, default = 94377984) or {+-}size{KMGTP}:
    Last sector (94377984-1953525134, default = 1953525134) or {+-}size{KMGTP}:
    Current type is 'Linux filesystem'
    Hex code or GUID (L to show codes, Enter = 8300): 8300
    Changed type of partition to 'Linux filesystem'
    we can check the setup
    Command (? for help): p
    Disk /dev/sda: 1953525168 sectors, 931.5 GiB
    Logical sector size: 512 bytes
    Disk identifier (GUID): 6527769B-B4BC-408C-A45B-D2DAA4036620
    Partition table holds up to 128 entries
    First usable sector is 34, last usable sector is 1953525134
    Partitions will be aligned on 2048-sector boundaries
    Total free space is 2014 sectors (1007.0 KiB)
    Number Start (sector) End (sector) Size Code Name
    1 2048 6143 2.0 MiB EF02 BIOS boot partition
    2 6144 94377983 45.0 GiB 8300 Linux filesystem
    3 94377984 1953525134 886.5 GiB 8300 Linux filesystem
    and everything looks fine, we have the multiples of 8 starting sectors, so we write the changes
    Command (? for help): w
    Final checks complete. About to write GPT data. THIS WILL OVERWRITE EXISTING PARTITIONS!!
    Do you want to proceed? (Y/N): y
    OK; writing new GUID partition table (GPT) to /dev/sda.
    The operation has completed successfully.
    now we need to give the / and /home partitions a format, I choose ext4 and ask for a 4096 block size just in case we have a "lying" unit (not my case but I prefer to write down the most general command)
    # mkfs.ext4 -b 4096 /dev/sda2
    mke2fs 1.42.6 (21-Sep-2012)
    Filesystem label=
    OS type: Linux
    Block size=4096 (log=2)
    Fragment size=4096 (log=2)
    Stride=0 blocks, Stripe width=0 blocks
    2949120 inodes, 11796480 blocks
    589824 blocks (5.00%) reserved for the super user
    First data block=0
    Maximum filesystem blocks=4294967296
    360 block groups
    32768 blocks per group, 32768 fragments per group
    8192 inodes per group
    Superblock backups stored on blocks:
    32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
    4096000, 7962624, 11239424
    Allocating group tables: done
    Writing inode tables: done
    Creating journal (32768 blocks): done
    Writing superblocks and filesystem accounting information: done
    and the same thing for /dev/sda3 .
    Check with gdisk and parted that everything is fine, is this all right to start the install ??
    # gdisk -l /dev/sda
    GPT fdisk (gdisk) version 0.8.5
    Partition table scan:
    MBR: protective
    BSD: not present
    APM: not present
    GPT: present
    Found valid GPT with protective MBR; using GPT.
    Disk /dev/sda: 1953525168 sectors, 931.5 GiB
    Logical sector size: 512 bytes
    Disk identifier (GUID): 6527769B-B4BC-408C-A45B-D2DAA4036620
    Partition table holds up to 128 entries
    First usable sector is 34, last usable sector is 1953525134
    Partitions will be aligned on 2048-sector boundaries
    Total free space is 2014 sectors (1007.0 KiB)
    Number Start (sector) End (sector) Size Code Name
    1 2048 6143 2.0 MiB EF02 BIOS boot partition
    2 6144 94377983 45.0 GiB 8300 Linux filesystem
    3 94377984 1953525134 886.5 GiB 8300 Linux filesystem
    # parted /dev/sda
    GNU Parted 3.1
    Using /dev/sda
    Welcome to GNU Parted! Type 'help' to view a list of commands.
    (parted) print
    Model: ATA WDC WD10EZEX-00R (scsi)
    Disk /dev/sda: 1000GB
    Sector size (logical/physical): 512B/4096B
    Partition Table: gpt
    Disk Flags:
    Number Start End Size File system Name Flags
    1 1049kB 3146kB 2097kB BIOS boot partition bios_grub
    2 3146kB 48.3GB 48.3GB ext4 Linux filesystem
    3 48.3GB 1000GB 952GB ext4 Linux filesystem
    Last edited by karamaz0v (2012-12-06 06:39:45)

    Your partitions look fine from an Advanced Format point of view. The test is simple: Are all your partitions' start points, as measured in sectors, divisible by 8? Yours are.
    karamaz0v wrote:what confused me a bit, was that I saw a lot of setups with the BIOS boot partition, and also a 200 MB EFI one. Having a BIOS system, I think I don't need the EFI one.
    Some people do this because they're unclear of their requirements. Others do it because they want to have the option of switching boot modes between BIOS/legacy and EFI. With both types of boot loader installed, you can choose on a boot-by-boot basis which way to start the computer, assuming it supports both boot modes.

  • EFI partition deleted after removal of dual boot of OSX10.8 and Ubuntu/Linux Mint - using rEFIt

    so, i recently installed ubuntu to check out the advances in the linux world since i last looked into them 10+ years ago... very impressed, but when i tried to delete ubuntu and remove the various partitions (which i was able to do just fine using gparted) reFIT still displayed the **** linux logo from the install i deleted....
    OSX still boots fine... a install of Linux Mint i have on another partition(s) still boots fine ... everything appears to work... but i want to know what the possible issues are so i can be prepared...
    this is frustrating...
    so i went in and looked around with the remaining partitions and noticed the EFI partition which hadn't shown before i mistakenly tried to install another distro over ubuntu after wiping the partition it was on...
    so i erased the EFI partition hoping that this would remove the g-damned hold out linux boot logo in reFIT... it didn't... now i suppose i can go back in and create a new EFI partition through gparted but that stupid linux logo will still be there... and i'll have another problem of getting the proper information back onto the EFI partition, which i am unsure of how to do, or where to even dig up the proper information...
    i want to edit my boot mbr or grub or whatever the eff apple comps use as a boot record so that (or i am using as a boot record since i'm using reFIT) to get rid of this **** logo, so i can install another distro of linux and probably windows without having the **** supernumerary logo...
    i would rather not wipe the whole drive (aka the primary partition the recovery partition) and do a fresh new install of os x (mountain lion) because i have OSX set up just the way i want it for personal use and work use... all my various tools and so on...
    i don't use time machine and can't do a "restore" from a previous back up...
    some one please help me out here, what are my options? am i going to have to bite the bullet and do a wipe of the entire drive and all its partitions to get my MBP back to 'normal'???
    PS - using a macbook pro late 2011, standard specs, 13"...

    stqn wrote:
    Expi1 wrote:Thanks, I'm mostly struggling with how to partition for Arch and then how to do the bootloader. I'm using Win8 64-bit and from what I understand a Legacy BIOS bootloader. I'm not entirely sure what I should be partitioning the C: into, I've done partitions before, just not for Arch and then I'm not sure whether to use GRUB or syslinux, or if I even need those. Or if I need to use GPT or MBR?
    Your disk is already partitionned so you don’t have to choose between GPT or MBR, the choice is already made.
    You don’t partition “C:”, that is the name of a Windows partition. You partition a drive.
    Grub or syslinux, use whatever the beginners guide tells you to. Personally I think syslinux is simpler which is why I’m using it (but I’m not dual-booting, if that matters).
    You’re not saying what your problem is with partitionning, so it’s hard to help.
    Thanks for getting back to me, I'm not sure if I just create one large partition for Archlinux or if I have to create multiple? Where I'm also confused is with the Creating Filesystems part of the guide. I don't understand how I'd do this in Windows, or what /dev/sda1 is referring to.
    As for the bootloader part, the Beginner's Guide gives you a choice between syslinux and grub, what I'm not sure about is which to use considering I'm dualbooting. How it will affect my windows bootloader, do I disregard that and use GRUB now? I'm unclear on how that works.
    I'm also aware I need to disable Secure Boot, I just searched my BIOS options and couldn't find anything remotely relating to that, so I'm assuming it's not an issue since this computer was originally on Windows 7 anyway?
    Thanks again, Expi.
    Last edited by Expi1 (2014-03-06 19:54:30)

  • How to efficiently get hold of N randomly selected keys out of X?

    I am writing some benchmark programs for Coherence caches and would need a way to as efficently as possible get hold of a "fairly random" selection of N keys from the cache out of the total X keys (where X >> N).
    With "fairly random" I am in particular looking for a way to get keys somewhat uniformly spread over all partitions.
    First i tried picking the first N keys obtained when iterating the key-set but they all seemed to come from just a few partitions (perhaps iteration is performed partition by partition?). Next I tried some algortihms I have used in the past to pick random keys from in memory-map (where one basically iterate and if a randomly generated value between 0.0 and 1.0 exceed a percentage calculatwed as the factor N/X the key is included. This does work (one may occasionally need to iterate the map more than once) but is VERY slow since iterating the key-set of a large cache remotly is kind of expensive.
    All sugestions are warmly appreciated - the best would be solutions that do not require anything to be added to the pof-config (i.e. not rely on custome aggregators or invocables etc) - this because I would liek to be able to easilly use my benchmark as part of several applications without having to modify there configuration files!
    /Magnus
    Edited by: MagnusE on Aug 7, 2009 10:21 AM

    Hi Magnus,
    you can go the other way round:
    With key-association you can ensure that your request goes to the partition you want it to go. You just need to generate a reverse mapping array between partition ids and integer associated key values which are mapped to that partititon.
    You can use this method for it:
    public static int[] generateReverseAssociatedKeysForService(DistributedCacheService service) {
         KeyPartitioningStrategy keyPartitioningStrategy = service.getKeyPartitioningStrategy();
         int partitionCount = service.getPartitionCount();
         int[] reverseKeys = new int[partitionCount];
         int i=1;
         while (partitionCount > 0) {
              Integer associatedKey = new Integer(i);
              int partitionId = keyPartitioningStrategy.getKeyPartition(associatedKey);
              if (reverseKeys[partitionId] == 0) {
                   reverseKeys[partitionId] = i;
                   --partitionCount;
              ++i;
         return reverseKeys;
    }After this, you generate an equal amount of entries for each partitions with composite keys which implement key association in a way that it returns an integer which maps to your designated partition id to serve as your data. Alternatively you can sort an existing key-set into per-partition keysets.
    After this, you just generate evenly spread random numbers between 0 and (partitionCount - 1) (both inclusive) which random number you use as an index to the reverse map to get an associated key value. Then you can generate another random number if you have multiple keys within a partition, or choose a key from the per-partition keyset for that partition if you have a set of existing keys.
    This way you get keys which are as evenly spread between partitions as your random generator generating your associated key indexes is spread.
    Best regards,
    Robert
    Edited by: robvarga on Aug 7, 2009 11:55 AM
    Added some more ideas and method implementation.

  • How to Dual Display with Dell U2711

    Hi,
    I am looking to connect my iMac (late 2013) to a Dell U2711 in a dual display configuration. I'd like to be able to use all 2560x1440 pixels of the Dell.
    the Dell has DVI-D (dual channel), Displayport (not mini displayport), HDMI and VGA.
    which port will give me the cleanest picture and best performance and what cable do I need to buy ? (obviously thunderbolt to something...)
    thanks !

    stqn wrote:
    Expi1 wrote:Thanks, I'm mostly struggling with how to partition for Arch and then how to do the bootloader. I'm using Win8 64-bit and from what I understand a Legacy BIOS bootloader. I'm not entirely sure what I should be partitioning the C: into, I've done partitions before, just not for Arch and then I'm not sure whether to use GRUB or syslinux, or if I even need those. Or if I need to use GPT or MBR?
    Your disk is already partitionned so you don’t have to choose between GPT or MBR, the choice is already made.
    You don’t partition “C:”, that is the name of a Windows partition. You partition a drive.
    Grub or syslinux, use whatever the beginners guide tells you to. Personally I think syslinux is simpler which is why I’m using it (but I’m not dual-booting, if that matters).
    You’re not saying what your problem is with partitionning, so it’s hard to help.
    Thanks for getting back to me, I'm not sure if I just create one large partition for Archlinux or if I have to create multiple? Where I'm also confused is with the Creating Filesystems part of the guide. I don't understand how I'd do this in Windows, or what /dev/sda1 is referring to.
    As for the bootloader part, the Beginner's Guide gives you a choice between syslinux and grub, what I'm not sure about is which to use considering I'm dualbooting. How it will affect my windows bootloader, do I disregard that and use GRUB now? I'm unclear on how that works.
    I'm also aware I need to disable Secure Boot, I just searched my BIOS options and couldn't find anything remotely relating to that, so I'm assuming it's not an issue since this computer was originally on Windows 7 anyway?
    Thanks again, Expi.
    Last edited by Expi1 (2014-03-06 19:54:30)

  • ISO Burn CD Failure

    Hi All,
    I keep getting the blue screen and a flashing cursor, but no install options. I've tried burning at a low speed, and from different burn devices(that I know are ok), and still the same. 1 CD even gave a "can't find boot.bin" error. Anyone else experienced this.? Cheers.
    coolboarderguy

    after the 4th burned CD, from yet another box/writer,
    I still get the cannot find boot.bin error
    message..below is what is in Tools on the CD,
    [root@localhost ~]# cd /media/cdrecorder
    [root@localhost cdrecorder]# ls
    Copyright JDS-THIRDPARTYLICENSEREADME Solaris_10
    [root@localhost cdrecorder]# cd Solaris_10
    [root@localhost Solaris_10]# ls
    Docs Misc Patches Product Tools
    [root@localhost Solaris_10]# cd Tools
    [root@localhost Tools]# ls
    add_install_client Boot dial rm_install_client
    setup_install_server
    [root@localhost Tools]# cat Boot
    cat: Boot: No such file or directory
    [root@localhost Tools]# cd Boot
    -bash: cd: Boot: No such file or directory
    [root@localhost Tools]#The issue with the "Boot" file is an expected problem. It's a
    symbolic link that points to "../../../s0" and this link is intended
    to be used with the Solaris "vold" daemon, once the system is
    installed. This symbolic link won't work in a foreign OS, because
    it probably points to a non existing file / path.
    (did you run the above commands on a ***BSD or Linux box?)
    There is a UFS root filesystem (using little endian byte ordering)
    on the CD boot media, and this filesystem contains the
    /boot/solaris/boot.bin file.
    The filesystem that you've been looking at is the ISO9660/Rock-
    Ridge filesystem part, it will be mounted on the /cdrom
    subdirectory in the UFS root filesystem during installation.
    I'm not sure if Linux is able to mount Solaris x86 UFS filesystems.
    (from the Solaris x86 installation CD).

  • Lots of errors in update

    Hi
    after a long time today I tried to update my arch system. I removed bin and sbin and /usr/sbin directories and perform the update. now I get this messy error which I have no idea on how to fix it.
    error: failed to commit transaction (conflicting files)
    glibc: /usr/bin/iconvconfig exists in filesystem
    glibc: /usr/bin/nscd exists in filesystem
    glibc: /usr/bin/sln exists in filesystem
    glibc: /usr/bin/zdump exists in filesystem
    glibc: /usr/bin/zic exists in filesystem
    bash: /usr/bin/sh exists in filesystem
    cracklib: /usr/bin/cracklib-check exists in filesystem
    cracklib: /usr/bin/cracklib-format exists in filesystem
    cracklib: /usr/bin/cracklib-packer exists in filesystem
    cracklib: /usr/bin/cracklib-unpacker exists in filesystem
    cracklib: /usr/bin/create-cracklib-dict exists in filesystem
    pam: /usr/bin/mkhomedir_helper exists in filesystem
    pam: /usr/bin/pam_tally exists in filesystem
    pam: /usr/bin/pam_tally2 exists in filesystem
    pam: /usr/bin/pam_timestamp_check exists in filesystem
    pam: /usr/bin/unix_chkpwd exists in filesystem
    pam: /usr/bin/unix_update exists in filesystem
    libcap: /usr/bin/capsh exists in filesystem
    libcap: /usr/bin/getcap exists in filesystem
    libcap: /usr/bin/getpcaps exists in filesystem
    libcap: /usr/bin/setcap exists in filesystem
    kmod: /usr/bin/depmod exists in filesystem
    kmod: /usr/bin/modprobe exists in filesystem
    shadow: /usr/bin/chgpasswd exists in filesystem
    shadow: /usr/bin/chpasswd exists in filesystem
    shadow: /usr/bin/groupadd exists in filesystem
    shadow: /usr/bin/groupdel exists in filesystem
    shadow: /usr/bin/groupmems exists in filesystem
    shadow: /usr/bin/groupmod exists in filesystem
    shadow: /usr/bin/groups exists in filesystem
    shadow: /usr/bin/grpck exists in filesystem
    shadow: /usr/bin/grpconv exists in filesystem
    shadow: /usr/bin/grpunconv exists in filesystem
    shadow: /usr/bin/newusers exists in filesystem
    shadow: /usr/bin/nologin exists in filesystem
    shadow: /usr/bin/pwck exists in filesystem
    shadow: /usr/bin/pwconv exists in filesystem
    shadow: /usr/bin/pwunconv exists in filesystem
    shadow: /usr/bin/useradd exists in filesystem
    shadow: /usr/bin/userdel exists in filesystem
    shadow: /usr/bin/usermod exists in filesystem
    util-linux: /usr/bin/addpart exists in filesystem
    util-linux: /usr/bin/agetty exists in filesystem
    util-linux: /usr/bin/blkid exists in filesystem
    util-linux: /usr/bin/blockdev exists in filesystem
    util-linux: /usr/bin/cfdisk exists in filesystem
    util-linux: /usr/bin/chcpu exists in filesystem
    util-linux: /usr/bin/ctrlaltdel exists in filesystem
    util-linux: /usr/bin/delpart exists in filesystem
    util-linux: /usr/bin/dmesg exists in filesystem
    util-linux: /usr/bin/fdformat exists in filesystem
    util-linux: /usr/bin/fdisk exists in filesystem
    util-linux: /usr/bin/findfs exists in filesystem
    util-linux: /usr/bin/findmnt exists in filesystem
    util-linux: /usr/bin/fsck exists in filesystem
    util-linux: /usr/bin/fsck.cramfs exists in filesystem
    util-linux: /usr/bin/fsck.minix exists in filesystem
    util-linux: /usr/bin/fsfreeze exists in filesystem
    util-linux: /usr/bin/fstrim exists in filesystem
    util-linux: /usr/bin/hwclock exists in filesystem
    util-linux: /usr/bin/kill exists in filesystem
    util-linux: /usr/bin/ldattach exists in filesystem
    util-linux: /usr/bin/login exists in filesystem
    util-linux: /usr/bin/losetup exists in filesystem
    util-linux: /usr/bin/lsblk exists in filesystem
    util-linux: /usr/bin/mkfs exists in filesystem
    util-linux: /usr/bin/mkfs.bfs exists in filesystem
    util-linux: /usr/bin/mkfs.cramfs exists in filesystem
    util-linux: /usr/bin/mkfs.minix exists in filesystem
    util-linux: /usr/bin/mkswap exists in filesystem
    util-linux: /usr/bin/more exists in filesystem
    util-linux: /usr/bin/mount exists in filesystem
    util-linux: /usr/bin/mountpoint exists in filesystem
    util-linux: /usr/bin/partx exists in filesystem
    util-linux: /usr/bin/pivot_root exists in filesystem
    util-linux: /usr/bin/raw exists in filesystem
    util-linux: /usr/bin/readprofile exists in filesystem
    util-linux: /usr/bin/resizepart exists in filesystem
    util-linux: /usr/bin/rtcwake exists in filesystem
    util-linux: /usr/bin/sfdisk exists in filesystem
    util-linux: /usr/bin/su exists in filesystem
    util-linux: /usr/bin/sulogin exists in filesystem
    util-linux: /usr/bin/swaplabel exists in filesystem
    util-linux: /usr/bin/swapoff exists in filesystem
    util-linux: /usr/bin/swapon exists in filesystem
    util-linux: /usr/bin/switch_root exists in filesystem
    util-linux: /usr/bin/umount exists in filesystem
    util-linux: /usr/bin/uuidd exists in filesystem
    util-linux: /usr/bin/vigr exists in filesystem
    util-linux: /usr/bin/vipw exists in filesystem
    util-linux: /usr/bin/wdctl exists in filesystem
    util-linux: /usr/bin/wipefs exists in filesystem
    e2fsprogs: /usr/bin/badblocks exists in filesystem
    e2fsprogs: /usr/bin/debugfs exists in filesystem
    e2fsprogs: /usr/bin/dumpe2fs exists in filesystem
    e2fsprogs: /usr/bin/e2freefrag exists in filesystem
    e2fsprogs: /usr/bin/e2fsck exists in filesystem
    e2fsprogs: /usr/bin/e2image exists in filesystem
    e2fsprogs: /usr/bin/e2label exists in filesystem
    e2fsprogs: /usr/bin/e2undo exists in filesystem
    e2fsprogs: /usr/bin/e4defrag exists in filesystem
    e2fsprogs: /usr/bin/filefrag exists in filesystem
    e2fsprogs: /usr/bin/fsck.ext2 exists in filesystem
    e2fsprogs: /usr/bin/fsck.ext3 exists in filesystem
    e2fsprogs: /usr/bin/fsck.ext4 exists in filesystem
    e2fsprogs: /usr/bin/fsck.ext4dev exists in filesystem
    e2fsprogs: /usr/bin/logsave exists in filesystem
    e2fsprogs: /usr/bin/mke2fs exists in filesystem
    e2fsprogs: /usr/bin/mkfs.ext2 exists in filesystem
    e2fsprogs: /usr/bin/mkfs.ext3 exists in filesystem
    e2fsprogs: /usr/bin/mkfs.ext4 exists in filesystem
    e2fsprogs: /usr/bin/mkfs.ext4dev exists in filesystem
    e2fsprogs: /usr/bin/mklost+found exists in filesystem
    e2fsprogs: /usr/bin/resize2fs exists in filesystem
    e2fsprogs: /usr/bin/tune2fs exists in filesystem
    libsasl: /usr/bin/pluginviewer exists in filesystem
    libsasl: /usr/bin/sasldblistusers2 exists in filesystem
    libsasl: /usr/bin/saslpasswd2 exists in filesystem
    keyutils: /usr/bin/key.dns_resolver exists in filesystem
    keyutils: /usr/bin/keyctl exists in filesystem
    keyutils: /usr/bin/request-key exists in filesystem
    krb5: /usr/bin/gss-server exists in filesystem
    krb5: /usr/bin/kadmin.local exists in filesystem
    krb5: /usr/bin/kadmind exists in filesystem
    krb5: /usr/bin/kdb5_ldap_util exists in filesystem
    krb5: /usr/bin/kdb5_util exists in filesystem
    krb5: /usr/bin/kprop exists in filesystem
    krb5: /usr/bin/kpropd exists in filesystem
    krb5: /usr/bin/kproplog exists in filesystem
    krb5: /usr/bin/krb5-send-pr exists in filesystem
    krb5: /usr/bin/krb5kdc exists in filesystem
    krb5: /usr/bin/sim_server exists in filesystem
    krb5: /usr/bin/sserver exists in filesystem
    krb5: /usr/bin/uuserver exists in filesystem
    avahi: /usr/bin/avahi-autoipd exists in filesystem
    avahi: /usr/bin/avahi-daemon exists in filesystem
    avahi: /usr/bin/avahi-dnsconfd exists in filesystem
    gconf: /usr/bin/gconfpkg exists in filesystem
    pciutils: /usr/bin/lspci exists in filesystem
    pciutils: /usr/bin/setpci exists in filesystem
    alsa-utils: /usr/bin/alsactl exists in filesystem
    apache: /usr/bin/ab exists in filesystem
    apache: /usr/bin/apachectl exists in filesystem
    apache: /usr/bin/apxs exists in filesystem
    apache: /usr/bin/checkgid exists in filesystem
    apache: /usr/bin/dbmmanage exists in filesystem
    apache: /usr/bin/envvars exists in filesystem
    apache: /usr/bin/envvars-std exists in filesystem
    apache: /usr/bin/htcacheclean exists in filesystem
    apache: /usr/bin/htdbm exists in filesystem
    apache: /usr/bin/htdigest exists in filesystem
    apache: /usr/bin/htpasswd exists in filesystem
    apache: /usr/bin/httpd exists in filesystem
    apache: /usr/bin/httpd.itk exists in filesystem
    apache: /usr/bin/httpd.worker exists in filesystem
    apache: /usr/bin/httxt2dbm exists in filesystem
    apache: /usr/bin/logresolve exists in filesystem
    apache: /usr/bin/rotatelogs exists in filesystem
    apache: /usr/bin/suexec exists in filesystem
    icu: /usr/bin/genccode exists in filesystem
    icu: /usr/bin/gencmn exists in filesystem
    icu: /usr/bin/gennorm2 exists in filesystem
    icu: /usr/bin/gensprep exists in filesystem
    icu: /usr/bin/icupkg exists in filesystem
    ca-certificates: /usr/bin/update-ca-certificates exists in filesystem
    v4l-utils: /usr/bin/v4l2-dbg exists in filesystem
    gnupg: /usr/bin/addgnupghome exists in filesystem
    gnupg: /usr/bin/applygnupgdefaults exists in filesystem
    cdrkit: /usr/bin/netscsid exists in filesystem
    gpm: /usr/bin/gpm exists in filesystem
    ca-certificates-java: /usr/bin/init-jks-keystore exists in filesystem
    rtmpdump: /usr/bin/rtmpgw exists in filesystem
    rtmpdump: /usr/bin/rtmpsrv exists in filesystem
    rtmpdump: /usr/bin/rtmpsuck exists in filesystem
    cifs-utils: /usr/bin/cifs.idmap exists in filesystem
    cifs-utils: /usr/bin/cifs.upcall exists in filesystem
    cpupower: /usr/bin/cpufreq-bench exists in filesystem
    cronie: /usr/bin/anacron exists in filesystem
    cronie: /usr/bin/crond exists in filesystem
    device-mapper: /usr/bin/dmeventd exists in filesystem
    device-mapper: /usr/bin/dmsetup exists in filesystem
    cryptsetup: /usr/bin/cryptsetup exists in filesystem
    cryptsetup: /usr/bin/cryptsetup-reencrypt exists in filesystem
    cryptsetup: /usr/bin/veritysetup exists in filesystem
    iptables: /usr/bin/ip6tables exists in filesystem
    iptables: /usr/bin/ip6tables-restore exists in filesystem
    iptables: /usr/bin/ip6tables-save exists in filesystem
    iptables: /usr/bin/iptables exists in filesystem
    iptables: /usr/bin/iptables-restore exists in filesystem
    iptables: /usr/bin/iptables-save exists in filesystem
    iptables: /usr/bin/xtables-multi exists in filesystem
    iproute2: /usr/bin/arpd exists in filesystem
    iproute2: /usr/bin/bridge exists in filesystem
    iproute2: /usr/bin/ctstat exists in filesystem
    iproute2: /usr/bin/genl exists in filesystem
    iproute2: /usr/bin/ifcfg exists in filesystem
    iproute2: /usr/bin/ifstat exists in filesystem
    iproute2: /usr/bin/ip exists in filesystem
    iproute2: /usr/bin/lnstat exists in filesystem
    iproute2: /usr/bin/nstat exists in filesystem
    iproute2: /usr/bin/routef exists in filesystem
    iproute2: /usr/bin/routel exists in filesystem
    iproute2: /usr/bin/rtacct exists in filesystem
    iproute2: /usr/bin/rtmon exists in filesystem
    iproute2: /usr/bin/rtpr exists in filesystem
    iproute2: /usr/bin/rtstat exists in filesystem
    iproute2: /usr/bin/ss exists in filesystem
    iproute2: /usr/bin/tc exists in filesystem
    dhclient: /usr/bin/dhclient exists in filesystem
    dhclient: /usr/bin/dhclient-script exists in filesystem
    dhcpcd: /usr/bin/dhcpcd exists in filesystem
    dosfstools: /usr/bin/dosfsck exists in filesystem
    dosfstools: /usr/bin/dosfslabel exists in filesystem
    dosfstools: /usr/bin/fsck.msdos exists in filesystem
    dosfstools: /usr/bin/fsck.vfat exists in filesystem
    dosfstools: /usr/bin/mkdosfs exists in filesystem
    dosfstools: /usr/bin/mkfs.msdos exists in filesystem
    dosfstools: /usr/bin/mkfs.vfat exists in filesystem
    procps-ng: /usr/bin/ps exists in filesystem
    procps-ng: /usr/bin/sysctl exists in filesystem
    pm-utils: /usr/bin/pm-hibernate exists in filesystem
    pm-utils: /usr/bin/pm-powersave exists in filesystem
    pm-utils: /usr/bin/pm-suspend exists in filesystem
    pm-utils: /usr/bin/pm-suspend-hybrid exists in filesystem
    usbmuxd: /usr/bin/usbmuxd exists in filesystem
    wpa_supplicant: /usr/bin/wpa_cli exists in filesystem
    wpa_supplicant: /usr/bin/wpa_passphrase exists in filesystem
    wpa_supplicant: /usr/bin/wpa_supplicant exists in filesystem
    ppp: /usr/bin/chat exists in filesystem
    ppp: /usr/bin/plog exists in filesystem
    ppp: /usr/bin/pppd exists in filesystem
    ppp: /usr/bin/pppdump exists in filesystem
    ppp: /usr/bin/pppoe-discovery exists in filesystem
    ppp: /usr/bin/pppstats exists in filesystem
    networkmanager: /usr/bin/NetworkManager exists in filesystem
    fuse: /usr/bin/fusermount exists in filesystem
    fuse: /usr/bin/mount.fuse exists in filesystem
    fuse: /usr/bin/ulockmgr_server exists in filesystem
    rtkit: /usr/bin/rtkitctl exists in filesystem
    gdm: /usr/bin/gdm exists in filesystem
    libatasmart: /usr/bin/skdump exists in filesystem
    libatasmart: /usr/bin/sktest exists in filesystem
    udisks2: /usr/bin/umount.udisks2 exists in filesystem
    iputils: /usr/bin/arping exists in filesystem
    iputils: /usr/bin/clockdiff exists in filesystem
    iputils: /usr/bin/rarpd exists in filesystem
    iputils: /usr/bin/rdisc exists in filesystem
    iputils: /usr/bin/tftpd exists in filesystem
    iputils: /usr/bin/tracepath exists in filesystem
    iputils: /usr/bin/tracepath6 exists in filesystem
    grub: /usr/bin/grub-bios-setup exists in filesystem
    grub: /usr/bin/grub-install exists in filesystem
    grub: /usr/bin/grub-mkconfig exists in filesystem
    grub: /usr/bin/grub-mknetdir exists in filesystem
    grub: /usr/bin/grub-ofpathname exists in filesystem
    grub: /usr/bin/grub-probe exists in filesystem
    grub: /usr/bin/grub-reboot exists in filesystem
    grub: /usr/bin/grub-set-default exists in filesystem
    grub: /usr/bin/grub-sparc64-setup exists in filesystem
    inetutils: /usr/bin/dnsdomainname exists in filesystem
    inetutils: /usr/bin/ftpd exists in filesystem
    inetutils: /usr/bin/rlogind exists in filesystem
    inetutils: /usr/bin/rshd exists in filesystem
    inetutils: /usr/bin/talkd exists in filesystem
    inetutils: /usr/bin/telnetd exists in filesystem
    jfsutils: /usr/bin/fsck.jfs exists in filesystem
    jfsutils: /usr/bin/jfs_debugfs exists in filesystem
    jfsutils: /usr/bin/jfs_fsck exists in filesystem
    jfsutils: /usr/bin/jfs_fscklog exists in filesystem
    jfsutils: /usr/bin/jfs_logdump exists in filesystem
    jfsutils: /usr/bin/jfs_mkfs exists in filesystem
    jfsutils: /usr/bin/jfs_tune exists in filesystem
    jfsutils: /usr/bin/mkfs.jfs exists in filesystem
    kexec-tools: /usr/bin/kdump exists in filesystem
    kexec-tools: /usr/bin/kexec exists in filesystem
    kexec-tools: /usr/bin/vmcore-dmesg exists in filesystem
    libbonobo: /usr/bin/bonobo-activation-sysconf exists in filesystem
    tar: /usr/bin/tar exists in filesystem
    lirc-utils: /usr/bin/lircd exists in filesystem
    lirc-utils: /usr/bin/lircmd exists in filesystem
    logrotate: /usr/bin/logrotate exists in filesystem
    lsof: /usr/bin/lsof exists in filesystem
    lvm2: /usr/bin/blkdeactivate exists in filesystem
    lvm2: /usr/bin/fsadm exists in filesystem
    lvm2: /usr/bin/lvchange exists in filesystem
    lvm2: /usr/bin/lvconvert exists in filesystem
    lvm2: /usr/bin/lvcreate exists in filesystem
    lvm2: /usr/bin/lvdisplay exists in filesystem
    lvm2: /usr/bin/lvextend exists in filesystem
    lvm2: /usr/bin/lvm exists in filesystem
    lvm2: /usr/bin/lvmchange exists in filesystem
    lvm2: /usr/bin/lvmconf exists in filesystem
    lvm2: /usr/bin/lvmdiskscan exists in filesystem
    lvm2: /usr/bin/lvmdump exists in filesystem
    lvm2: /usr/bin/lvmetad exists in filesystem
    lvm2: /usr/bin/lvmsadc exists in filesystem
    lvm2: /usr/bin/lvmsar exists in filesystem
    lvm2: /usr/bin/lvreduce exists in filesystem
    lvm2: /usr/bin/lvremove exists in filesystem
    lvm2: /usr/bin/lvrename exists in filesystem
    lvm2: /usr/bin/lvresize exists in filesystem
    lvm2: /usr/bin/lvs exists in filesystem
    lvm2: /usr/bin/lvscan exists in filesystem
    lvm2: /usr/bin/pvchange exists in filesystem
    lvm2: /usr/bin/pvck exists in filesystem
    lvm2: /usr/bin/pvcreate exists in filesystem
    lvm2: /usr/bin/pvdisplay exists in filesystem
    lvm2: /usr/bin/pvmove exists in filesystem
    lvm2: /usr/bin/pvremove exists in filesystem
    lvm2: /usr/bin/pvresize exists in filesystem
    lvm2: /usr/bin/pvs exists in filesystem
    lvm2: /usr/bin/pvscan exists in filesystem
    lvm2: /usr/bin/vgcfgbackup exists in filesystem
    lvm2: /usr/bin/vgcfgrestore exists in filesystem
    lvm2: /usr/bin/vgchange exists in filesystem
    lvm2: /usr/bin/vgck exists in filesystem
    lvm2: /usr/bin/vgconvert exists in filesystem
    lvm2: /usr/bin/vgcreate exists in filesystem
    lvm2: /usr/bin/vgdisplay exists in filesystem
    lvm2: /usr/bin/vgexport exists in filesystem
    lvm2: /usr/bin/vgextend exists in filesystem
    lvm2: /usr/bin/vgimport exists in filesystem
    lvm2: /usr/bin/vgimportclone exists in filesystem
    lvm2: /usr/bin/vgmerge exists in filesystem
    lvm2: /usr/bin/vgmknodes exists in filesystem
    lvm2: /usr/bin/vgreduce exists in filesystem
    lvm2: /usr/bin/vgremove exists in filesystem
    lvm2: /usr/bin/vgrename exists in filesystem
    lvm2: /usr/bin/vgs exists in filesystem
    lvm2: /usr/bin/vgscan exists in filesystem
    lvm2: /usr/bin/vgsplit exists in filesystem
    man-db: /usr/bin/accessdb exists in filesystem
    mdadm: /usr/bin/mdadm exists in filesystem
    mdadm: /usr/bin/mdassemble exists in filesystem
    mdadm: /usr/bin/mdmon exists in filesystem
    net-snmp: /usr/bin/snmpd exists in filesystem
    net-snmp: /usr/bin/snmptrapd exists in filesystem
    net-tools: /usr/bin/arp exists in filesystem
    net-tools: /usr/bin/ifconfig exists in filesystem
    net-tools: /usr/bin/ipmaddr exists in filesystem
    net-tools: /usr/bin/iptunnel exists in filesystem
    net-tools: /usr/bin/mii-tool exists in filesystem
    net-tools: /usr/bin/nameif exists in filesystem
    net-tools: /usr/bin/netstat exists in filesystem
    net-tools: /usr/bin/plipconfig exists in filesystem
    net-tools: /usr/bin/rarp exists in filesystem
    net-tools: /usr/bin/route exists in filesystem
    net-tools: /usr/bin/slattach exists in filesystem
    xinetd: /usr/bin/itox exists in filesystem
    xinetd: /usr/bin/xconv.pl exists in filesystem
    xinetd: /usr/bin/xinetd exists in filesystem
    netkit-bsd-finger: /usr/bin/in.fingerd exists in filesystem
    pptpclient: /usr/bin/pptp exists in filesystem
    pptpclient: /usr/bin/pptpsetup exists in filesystem
    vpnc: /usr/bin/vpnc exists in filesystem
    vpnc: /usr/bin/vpnc-disconnect exists in filesystem
    ntfs-3g: /usr/bin/mkntfs exists in filesystem
    ntfs-3g: /usr/bin/ntfsclone exists in filesystem
    ntfs-3g: /usr/bin/ntfscp exists in filesystem
    ntfs-3g: /usr/bin/ntfslabel exists in filesystem
    ntfs-3g: /usr/bin/ntfsresize exists in filesystem
    ntfs-3g: /usr/bin/ntfsundelete exists in filesystem
    openssh: /usr/bin/sshd exists in filesystem
    parted: /usr/bin/parted exists in filesystem
    parted: /usr/bin/partprobe exists in filesystem
    pcmciautils: /usr/bin/lspcmcia exists in filesystem
    pcmciautils: /usr/bin/pccardctl exists in filesystem
    vde2: /usr/bin/vde_tunctl exists in filesystem
    reiserfsprogs: /usr/bin/debugreiserfs exists in filesystem
    reiserfsprogs: /usr/bin/fsck.reiserfs exists in filesystem
    reiserfsprogs: /usr/bin/mkfs.reiserfs exists in filesystem
    reiserfsprogs: /usr/bin/mkreiserfs exists in filesystem
    reiserfsprogs: /usr/bin/reiserfsck exists in filesystem
    reiserfsprogs: /usr/bin/reiserfstune exists in filesystem
    reiserfsprogs: /usr/bin/resize_reiserfs exists in filesystem
    sane: /usr/bin/saned exists in filesystem
    sudo: /usr/bin/visudo exists in filesystem
    syslog-ng: /usr/bin/syslog-ng exists in filesystem
    syslog-ng: /usr/bin/syslog-ng-ctl exists in filesystem
    sysvinit-tools: /usr/bin/bootlogd exists in filesystem
    sysvinit-tools: /usr/bin/fstab-decode exists in filesystem
    sysvinit-tools: /usr/bin/killall5 exists in filesystem
    sysvinit-tools: /usr/bin/pidof exists in filesystem
    udisks: /usr/bin/umount.udisks exists in filesystem
    zvbi: /usr/bin/zvbid exists in filesystem
    vnstat: /usr/bin/vnstatd exists in filesystem
    xfsprogs: /usr/bin/fsck.xfs exists in filesystem
    xfsprogs: /usr/bin/mkfs.xfs exists in filesystem
    xfsprogs: /usr/bin/xfs_admin exists in filesystem
    xfsprogs: /usr/bin/xfs_bmap exists in filesystem
    xfsprogs: /usr/bin/xfs_check exists in filesystem
    xfsprogs: /usr/bin/xfs_copy exists in filesystem
    xfsprogs: /usr/bin/xfs_db exists in filesystem
    xfsprogs: /usr/bin/xfs_estimate exists in filesystem
    xfsprogs: /usr/bin/xfs_freeze exists in filesystem
    xfsprogs: /usr/bin/xfs_fsr exists in filesystem
    xfsprogs: /usr/bin/xfs_growfs exists in filesystem
    xfsprogs: /usr/bin/xfs_info exists in filesystem
    xfsprogs: /usr/bin/xfs_io exists in filesystem
    xfsprogs: /usr/bin/xfs_logprint exists in filesystem
    xfsprogs: /usr/bin/xfs_mdrestore exists in filesystem
    xfsprogs: /usr/bin/xfs_metadump exists in filesystem
    xfsprogs: /usr/bin/xfs_mkfile exists in filesystem
    xfsprogs: /usr/bin/xfs_ncheck exists in filesystem
    xfsprogs: /usr/bin/xfs_quota exists in filesystem
    xfsprogs: /usr/bin/xfs_repair exists in filesystem
    xfsprogs: /usr/bin/xfs_rtcp exists in filesystem
    Errors occurred, no packages were upgraded.
    whould you please help me out of these?
    thenk you.
    Last edited by jgvr (2013-10-08 10:06:49)

    jrussell wrote:Also, I don't think you are supposed to remove those directories.... Are you referring to this? https://www.archlinux.org/news/binaries … ervention/
    Judging from the output, I think that OP has a system from before that news post you linked and hasn't quite understood the news post correctly.
    @jgvr: I think you have missed this news update and haven't read the forums on how to do it, thus ending up with a borked system.
    My approach would be to move everything back to where it originally was, then upgrade everything (including AUR packages) except for glibc,bash and filesystem and see how far that gets you first. But as @Scimmia says, if you installation was from before Jan 2013, just re-install the whole thing.
    Last edited by clfarron4 (2013-10-08 21:22:52)

  • Tomcat writing files - access denied

    I've problem with my simple jsp. I just want to create file on server in custom directory. At my tomcat at localhost it works fine, but at my server doesn't - permisson denied. I've googled a bit and found the problem is (probably) fact, that tomcat is not running under a user with write permissions to that directory. But how to run tomcat under user with write permissons? It's running under ms windows 2003 server. I was not able to found how to fix this problem...Thanx a lot, if somebody knows. Or is there something like temp directory on server, where EVERYBODY can write?

    mil84 wrote:
    I've problem with my simple jsp. I just want to create file on server in custom directory. At my tomcat at localhost it works fine, but at my server doesn't - permisson denied. I've googled a bit and found the problem is (probably) fact, that tomcat is not running under a user with write permissions to that directory. But how to run tomcat under user with write permissons? It's running under ms windows 2003 server. The user account who runs Tomcat should have access to the specified filesystem part. Consult the docs of the underlying operating system.
    I was not able to found how to fix this problem...Thanx a lot, if somebody knows. Or is there something like temp directory on server, where EVERYBODY can write?
    String tmpdir = System.getProperty("java.io.tmpdir");

  • MPD starting and stopping at shutdown

    I have added mpd to my gnome3 startup programs by running gnome-session-properties and adding mpd ~/.mpd/mpd.conf but no dice, I have to run the command myself before I can play any music.
    My other issue is it causes my boot-down process to stall. I believe this is because my music in on a NAS. Switching to Alt+F8 on shut down I see it fails to unmount network file-systems because they are busy, then it stops the network, then when it gets to unmounting file-systems it just hangs at 'BUSY'.
    This is avoided if I remember to issue mpd --kill before a reboot or shutdown.
    I was thinking, looking at the other startup programs, maybe MPD will work if I point to the binary explicitly; i.e.  /usr/bin/mpd.

    Use netcfg or wicd and create a pre_down hook (https://wiki.archlinux.org/index.php/Ne … _up.2Fdown)
    Example for netcfg:
    /etc/network.d/interfaces/eth0
    PRE_DOWN="rc.d stop mpd; umount yournetworksharehere"
    You could also place those commands somewhere at the top of your /etc/rc.shutdown or /etc/rc.local.shutdown.
    You just have to find a place where the commands get executed before the filesystems are unmounted. I'd put it in rc.shutdown somewhere before the
    "stat_busy 'Unmounting Filesystems'" part.
    Regards,
    demian
    Last edited by demian (2011-05-26 06:59:35)

  • 2008.12 archboot test iso/img files

    Hi Arch community,
    Arch Linux (archboot creation tool) 2008.12-1, "Nepal" has been released.
    http://downloads.archlinux.de/iso/archboot/2008.12/
    (Thanks Pierre for hosting them in the meanwhile )
    This is a test run for the created files, please try to find showstoppers.
    If everything is alright, those files can be moved to the mirrors and torrents can be created.
    To avoid confusion, this is not an official arch linux release!
    It's an installation environment created with the archboot tools.
    Please report all bugs only to my email address.
    Thanks for testing.
    Have Fun
    greetings
    tpowa
    Changelog:
    GENERAL:
    - kernel 2.6.27.7 usage
    - pacman 3.2.1 usage
    - RAM  recommendations:
         * arch or arch64 boot image
           160 MB RAM i686/x86_64 (all packages selected, with swap partition)
         * lowmem or lowmem64 boot image
           64 MB RAM i686/x86_64 (all packages selected, with swap partition)
    FIXES:
    - merged in setup changes from installer.git
    - merged in documentation changes from installer.git
    - changed bootmessages
    - changed intel wireless hook to improve boot speed
    - fixed quickinst
    - added new tz script for setting date, time and zones
    - added some fixes to km
    - added setup startup on first login
    - added km and tz to setup dialogs
    - added dmraid dialog for mkinitcpio setup
    - added ntp to arch and arch64 install environment
    KNOWN ISSUES:
    - None
    ISO and USB image files are provided, which include
    i686 and x86_64 core repository. Please check md5sums before using them.
    ISO files are standard CD-burnable images.
        - Can be burned to CD(RW) media using most CD-burning utilities.
    IMG files are full raw disk images.
        - Intended for use with USB thumb drives.
        - Can be raw-written to a drive using 'dd' or similar utilities.
    Further documentation can be found on-disk and on the wiki.
    Have fun!
    greetings
    tpowa

    Tobias, you may have read on arch-general that I've been working on a totally refactored installer (installation framework).
    It's called AIF.  Basically I've taken the old /arch/setup from installer.git and totally refactored everything to make the codebase clean, modular and reusable.  Lately I've also been rewriting the whole blockdevice/filesystem part of the installer because it wasn't very good.  For more info I refer to http://dieter.plaetinck.be/AIF_the_bran … _Framework , http://archlinux.org/pipermail/arch-gen … 02541.html (albeit most of the info there is a bit outdated now) and http://github.com/Dieterbe/aif/tree/master
    I also maintain packages in aur ( http://aur.archlinux.org/packages.php?ID=21565 follows the master branch, where I pull in all the stabilized code, so I recommend this package)
    Right now AIF is mostly good for developers/power users who wish to make custom installation procedures.
    Towards the reglar user there isn't that much of a difference: the installer looks very similar. although under the hood 95% of the things are different.  Right now I'm also working on supporting lvm/dm_crypt.
    Anyway, if you're interested, I suggest you take a look at the code and if you like it you could maybe integrate AIF as an alternative, experimental installer. (it doesn't conflict with the other installer, it installs alongside)
    Last edited by Dieter@be (2008-12-11 10:27:18)

  • CRIO-9073 scan mode speed

    I am testing scan mode speed of a cRIO module.
    It seems I cannot make it operate reliable under 4 ms loops.
    I'm just reading 6 parameters and writing 7 digital outputs within the timed loop.
    Is this to be expected from this hardware ?
    Martin

    Hi Martin
    There are many factors that we need to consider programmatically, for example if you are using a while loop, timed loop, a timing VI inside of the loop (wait, wait until next ms multiple, etc). also we need to keep in mind how is reading the parameter and writing the digital output if there is any dependency or code that need or is being executed in the middle.
    Last but not the least as you said there might also be hardware limitations in order to confirm this we might need to know which modules you are using.
    One way to determine which is the function that is taking longer to execute, or is delaying your application, is to benchmark a part of your code or the whole code. Take a look to this forum and keep in mind that in order to disable a part of the code without deleting the code is to use the diagram disable structure.
    Regards
    Esteban R.

  • Flex-based podcast player sample

    I'm looking for sample code for working with sound in Flex 3.
    The Podcast Player example referred to in the docs and downloadable
    as the zip Programming_ActionScript3.0_samples.zip seems to be
    geared to flash and doesn't include the .mxml files and possibly
    other necessary files. Is there a complete Flex-based version of
    this sample available?
    Any pointers to other Flex sound coding samples would be
    great as well.

    Hi- In my AIR-in-FlexBuilder beta demo I write a little music
    player from scratch. My voiceover cuts out midway through but you
    can see how I write the code, including how to use Sound and
    SoundChannel. This is all applicable to web-based Flex apps as
    well, except for the local filesystem part.
    http://labs.adobe.com/technologies/flex/videos/airinbuilder
    Does that help?
    -Tom

  • Filesystems benchmarked: EXT3 vs EXT4 vs XFS vs BTRFS

    I wondered across this fine artical this morning, and thought I would share it with the community.
    Quote:
    Let's start from the most obvious: the best balanced filesystem seems to be the mature, almost aging EXT3. This is natural, as it received most cumulative improvements over a long period of time. It has very good sequential and random write speeds and reasonable read speed, factors that are of utmost importance on several different tasks. For example, if you plan to run a database server you are almost forced to use EXT3, as all other filesystems seems to have big problems with synchronized random write speed. Also, you can't go wrong with EXT3 if you use it on your workstation as its performances are quite good in a great amount of different jobs. Finally, EXT3 is more stable than the others FS as most of its bug are by now already worked out.
    However, this not means that EXT3 is the perfect FS: first, it that lacks some important features as delayed allocation and online compression. It lacks native snapshots capability also but you can use LVM to overcome this. It is more fragmentation-prone that EXT4 and XFS and it is very slow in creating/deleting large amount of files, denoting a not-so-good metadata handling. Moreover, it use more CPU cycles than EXT4 and XFS, but with todays CPU I don't think that this is a great problem. If you can live with these minor faults, EXT3 is the right filesystem for you.
    Please don't just read that one paragraph though, they have ten pages worth of detailed and varied benchmarks they used to form that opinion. And the artical is dated from the middle of last month, nice and recent
    Interesting stuff, I thought that ext4 would do better (not that it did poorly, but relative to ext3) And that btrfs wouldnt be as slow as it currently seems, though as the tester commented, it's a very new filesystem. Maybe Arch should ship btrfs as an install option? Help these guys iron out the bugs!

    fukawi2 wrote:
    Misfit138 wrote: Dodge RAM 2500 Cummins Turbodiesel FTW.
    F650 FTW
    Well if you go there, then I have to pull out my Chevy Kodiak Pickup.
    Last edited by Misfit138 (2010-12-04 02:13:59)

Maybe you are looking for