search for: xvdj

..., after a few research and IRC chat, I figured out that it's not weird, it's actually a normal and expected behavior (thanks for your help, z00dax). sdX is actually mapped to xvdX+4. There is a consistent offset of 4. Suppose you attach an ebs volume to /dev/sdf. It'll be translated to xvdj at the OS level. sdg to xvdk, sdh to xvdl and so on. Allright. After having figured the mystery out, it became easy to work on automations that deal with ebs volumes and file systems, such as volumes created, attached and mounted on the fly, snapshots that freeze file systems and so on... However...

...0,00 0,00 0,00 0,00 0,00 0,00 0,00 xvdh 0,00 0,00 0,00 0,00 0,00 0,00 0,00 0,00 0,00 0,00 0,00 0,00 0,00 xvdi 0,00 0,00 0,00 0,00 0,00 0,00 0,00 0,00 0,00 0,00 0,00 0,00 0,00 xvdj 0,00 0,00 0,00 0,00 0,00 0,00 0,00 0,00 0,00 0,00 0,00 0,00 0,00 dm-0 0,00 0,00 0,00 0,00 0,00 0,00 0,00 0,00 0,00 0,00 0,00 0,00 0,00 dm-1 0,00 0,00 0,00 0,00 0,00...

This is pretty ugly. I''m using puppet to install Oracle, ie an exec{} wrapped around: /u01/oracle_extract/linux.x64_11gR2_database/database/runInstaller -silent -responseFile /etc/oracle_response.rsp The problem is that the damn installer backgrounds itself and returns control to the shell. I tried putting the above command in a script, followed by a wait command, but that