Package: e2fsprogs Version: 1.42.5-1.1 Interesting behavior from: `mke2fs -J device=UUID=<uuid> /dev/sda2` when the UUID is on the device /dev/sda3, and device /dev/sda1 is swap space:
# mke2fs -j -t ext3 -O dir_index -J device=UUID=<uuid> /dev/sda2 mke2fs 1.42.5 (29-Jul-2012) mke2fs: Bad magic number in super-block while trying to open journal device /dev/sda1 # mke2fs -j -t ext3 -O dir_index -J device=LABEL=journal /dev/sda2 mke2fs 1.42.5 (29-Jul-2012) Using journal device's blocksize: 4096 Filesystem label=lair-/var I'm surprised mke2fs got confused by a swap device when telling it the UUID, but was just fine with either the LABEL or actual device. Oddly `tune2fs -J device=UUID=<uuid> /dev/sda2` didn't have a problem, only mke2fs did. Though I suppose tune2fs might have had access to the device number cached in the superblock (I had to reinitialize the journal, then point back to it). -- (\___(\___(\______ --=> 8-) EHM <=-- ______/)___/)___/) \BS ( | [email protected] PGP 87145445 | ) / \_CS\ | _____ -O #include <stddisclaimer.h> O- _____ | / _/ 8A19\___\_|_/58D2 7E3D DDF4 7BA6 <-PGP-> 41D1 B375 37D0 8714\_|_/___/5445 -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
