[arch-releng] 2010.04.05 snapshots ready for testing

[Chris Brannon]

Dieter Plaetinck wrote:
> can you maybe do an ls -alh, stat, and file on $1 as the first thing in
> process_filesystem?
*SNIP*
> that's really odd. so basically you are saying when the dm_crypt is
> created -b on it returns true, but a bit later -b on the same thing
> does not. please doublecheck that $fs_label is cryptoroot here.
> do a ls -alh, stat and file here also. so we can compare.

Ok, I added file, ls -al, and stat at both points.
It worked like a charm, even when aif is invoked
as aif -p interactive.
That log is the first attachment.

Next, I removed the file and ls -al calls, so we were left with only
the two stats.
I wanted to make it fail again, but it didn't oblige.
That log is the second attachment, partlog2.txt.
The stat following cryptsetup is different than the stat at the start
of process_filesystem.  In the first stat, you'll see
that /dev/mapper/cryptoroot is a block device.  It is at inode 7872.
The second stat shows that /dev/mapper/cryptoroot is a symlink, and it
is at inode 7949.

-- Chris

-------------- next part --------------
cryptsetup done, partition should be good to go.
$fs_label is cryptoroot
Executing file
/dev/mapper/cryptoroot: block special
Executing ls -al
lrwxrwxrwx 1 root root 7 Apr 10 21:15 /dev/mapper/cryptoroot -> ../dm-0
Executing stat
  File: `/dev/mapper/cryptoroot' -> `../dm-0'
  Size: 7         	Blocks: 0          IO Block: 4096   symbolic link
Device: eh/14d	Inode: 5187        Links: 1
Access: (0777/lrwxrwxrwx)  Uid: (    0/    root)   Gid: (    0/    root)
Access: 2010-04-10 21:15:07.233422243 +0000
Modify: 2010-04-10 21:15:06.926814599 +0000
Change: 2010-04-10 21:15:06.930083378 +0000
Starting process_filesystem
$1 is /dev/mapper/cryptoroot.
Executing file $1
/dev/mapper/cryptoroot: symbolic link to `../dm-0'
Executing ls -al $1
lrwxrwxrwx 1 root root 7 Apr 10 21:15 /dev/mapper/cryptoroot -> ../dm-0
Executing stat $1
  File: `/dev/mapper/cryptoroot' -> `../dm-0'
  Size: 7         	Blocks: 0          IO Block: 4096   symbolic link
Device: eh/14d	Inode: 5238        Links: 1
Access: (0777/lrwxrwxrwx)  Uid: (    0/    root)   Gid: (    0/    root)
Access: 2010-04-10 21:15:11.746746690 +0000
Modify: 2010-04-10 21:15:11.503398104 +0000
Change: 2010-04-10 21:15:11.503398104 +0000
-------------- next part --------------
cryptsetup done, partition should be good to go.
$fs_label is cryptoroot
Executing stat /dev/mapper/$fs_label
  File: `/dev/mapper/cryptoroot'
  Size: 0         	Blocks: 0          IO Block: 4096   block special file
Device: eh/14d	Inode: 7872        Links: 1     Device type: fe,0
Access: (0600/brw-------)  Uid: (    0/    root)   Gid: (    0/    root)
Access: 2010-04-10 21:55:33.439819465 +0000
Modify: 2010-04-10 21:55:33.439819465 +0000
Change: 2010-04-10 21:55:33.439819465 +0000
Starting process_filesystem
$1 is /dev/mapper/cryptoroot.
Executing stat $1
  File: `/dev/mapper/cryptoroot' -> `../dm-0'
  Size: 7         	Blocks: 0          IO Block: 4096   symbolic link
Device: eh/14d	Inode: 7949        Links: 1
Access: (0777/lrwxrwxrwx)  Uid: (    0/    root)   Gid: (    0/    root)
Access: 2010-04-10 21:55:42.526565516 +0000
Modify: 2010-04-10 21:55:42.509867907 +0000
Change: 2010-04-10 21:55:42.509867907 +0000