I hope this is truncated right. Had to write it in an editor and paste it!
CONCERNING THE FAILURE OF XFS-PARTITIONS TO OPEN ON BOOT
-CRYPTTAB-
I think I have found at least part of a solution:
The message at startup "unknown option luks" I consider as a notification more
than error. The 4th field in crypttab is optional and as long as the mechanism
for uncryption really opens the partition anyhow I can only delete the 4th
field changing the crypttab
from this:
#cr_krypto_kon /tmp/krypto_kon none none krypto_kon reiserfs
#cr_krypto_kon /tmp/krypto_kon none loop
#cr_krypto_pas /tmp/krypto_pas none loop
#cr_krypto_ark1 /tmp/krypto_arkiv none loop
#cr_krypto_ark2 /tmp/krypto_dev_hdb_kopi none loop
_dev_hdc6 /dev/hdc6 none luks
_dev_hdc7 /dev/hdc7 none luks
_dev_hdc8 /dev/hdc8 none luks
_dev_hdc9 /dev/hdc9 none luks
_dev_hdc10 /dev/hdc10 none luks
to this:
#cr_krypto_kon /tmp/krypto_kon none none krypto_kon reiserfs
#cr_krypto_kon /tmp/krypto_kon none loop
#cr_krypto_pas /tmp/krypto_pas none loop
#cr_krypto_ark1 /tmp/krypto_arkiv none loop
#cr_krypto_ark2 /tmp/krypto_dev_hdb_kopi none loop
_dev_hdc6 /dev/hdc6 none
_dev_hdc7 /dev/hdc7 none
_dev_hdc8 /dev/hdc8 none
_dev_hdc9 /dev/hdc9 none
_dev_hdc10 /dev/hdc10 none
Forget about the commented parts that belong to a previous setup with
file-containers to test out before further partition of harddisk was started.
By the way: The filecontainers (losetups) needed 'loop' in the 4th field to
function. But the partitons seem not need any specification of the 4th field to
be recogniced as LUKS-partitions.
-FSTAB-
As to the fstab this seems more interesting:
/dev/hdc5 / reiserfs acl,user_xattr 1 1
/dev/hdc2 swap swap defaults 0 0
proc /proc proc defaults 0 0
sysfs /sys sysfs noauto 0 0
debugfs /sys/kernel/debug debugfs noauto 0 0
usbfs /proc/bus/usb usbfs noauto 0 0
devpts /dev/pts devpts mode=0620,gid=5 0 0
/dev/fd0 /media/floppy auto noauto,user,sync 0 0
#/dev/mapper/cr_krypto_kon /krypt/KON reiserfs acl,user_xattr,noauto 0 0
#/dev/mapper/cr_krypto_pas /krypt/KON/pas reiserfs acl,user_xattr,noauto 0 0
#/dev/mapper/cr_krypto_ark1 /krypt/ark1 xfs acl,user_xattr,noauto 0 0
#/dev/mapper/cr_krypto_ark2 /krypt/ark2 xfs acl,user_xattr,noauto 0 0
/dev/mapper/_dev_hdc6 /krypt/KON reiserfs acl,user_xattr,noauto 0 0
/dev/mapper/_dev_hdc7 /krypt/KON/pas reiserfs acl,user_xattr,noauto 0 0
/dev/mapper/_dev_hdc8 /tmp reiserfs acl,user_xattr,noauto 0 0
/dev/mapper/_dev_hdc9 /krypt/ark1 xfs acl,user_xattr,noauto 0 0
/dev/mapper/_dev_hdc10 /krypt/ark2 xfs acl,user_xattr,noauto 0 0
The /var/log/messages notified that the 'acl' was unknown as to the XFS:
Jan 8 17:25:45 linux-wh8s kernel: SGI XFS with ACLs, security attributes,
realtime, large block numbers, no debug enabled
Jan 8 17:25:45 linux-wh8s kernel: SGI XFS Quota Management subsystem
Jan 8 17:25:45 linux-wh8s kernel: XFS: unknown mount option [acl].
The following message might have come from putting none on the 4th field to
test what happened (maybe just forget about it).The /var/log/warn had the same
notification:
/var/log/messages:
Jan 7 17:19:51 linux-wh8s kernel: XFS: bad magic number
Jan 7 17:19:51 linux-wh8s kernel: XFS: SB validate failed
/var/log/warn:
Jan 7 17:10:46 linux-wh8s kernel: XFS: bad magic number
Jan 7 17:10:46 linux-wh8s kernel: XFS: SB validate failed
/var/log/warn:
This came from the trying to open xfs on a filecontainer (note Dec 17):
Dec 17 15:22:54 linux-wh8s kernel: XFS: Filesystem dm-3 has duplicate UUID -
can't mount
Deleting the 'acl' from fstab gave this /var/log/message:
Jan 8 17:46:45 linux-wh8s kernel: SGI XFS with ACLs, security attributes,
realtime, large block numbers, no debug enabled
Jan 8 17:46:45 linux-wh8s kernel: SGI XFS Quota Management subsystem
Jan 8 17:46:45 linux-wh8s kernel: XFS: unknown mount option [user_xattr].
Jan 8 17:46:45 linux-wh8s kernel: XFS: unknown mount option [user_xattr].
So I deleted the user_xattr from the fstab too.
The new fstab look like this:
/dev/hdc5 / reiserfs acl,user_xattr 1 1
/dev/hdc2 swap swap defaults 0 0
proc /proc proc defaults 0 0
sysfs /sys sysfs noauto 0 0
debugfs /sys/kernel/debug debugfs noauto 0 0
usbfs /proc/bus/usb usbfs noauto 0 0
devpts /dev/pts devpts mode=0620,gid=5 0 0
/dev/fd0 /media/floppy auto noauto,user,sync 0 0
#/dev/mapper/cr_krypto_kon /krypt/KON reiserfs acl,user_xattr,noauto 0 0
#/dev/mapper/cr_krypto_pas /krypt/KON/pas reiserfs acl,user_xattr,noauto 0 0
#/dev/mapper/cr_krypto_ark1 /krypt/ark1 xfs acl,user_xattr,noauto 0 0
#/dev/mapper/cr_krypto_ark2 /krypt/ark2 xfs acl,user_xattr,noauto 0 0
/dev/mapper/_dev_hdc6 /krypt/KON reiserfs acl,user_xattr,noauto 0 0
/dev/mapper/_dev_hdc7 /krypt/KON/pas reiserfs acl,user_xattr,noauto 0 0
/dev/mapper/_dev_hdc8 /tmp reiserfs acl,user_xattr,noauto 0 0
/dev/mapper/_dev_hdc9 /krypt/ark1 xfs noauto 0 0
/dev/mapper/_dev_hdc10 /krypt/ark2 xfs noauto 0 0
Now, the xfs-partition was opened and there was error message promptwise or in
the /var/log/messages:
The boot.msg : "unknown crypttab option: 'luks'" disappeared.
messages :
Dec 15 16:16:44 linux-wh8s kernel: SGI XFS with ACLs, security attributes,
realtime, large block numbers, no debug enabled
Dec 15 16:16:44 linux-wh8s kernel: SGI XFS Quota Management subsystem
Dec 15 16:16:44 linux-wh8s kernel: Filesystem "dm-2": Disabling barriers, not
supported by the underlying device
Dec 15 16:16:44 linux-wh8s kernel: XFS mounting filesystem dm-2
Dec 15 16:16:44 linux-wh8s kernel: Ending clean XFS mount for filesystem: dm-2
By the way, messages from manual opening with luksOpen:
Jan 8 17:38:06 linux-wh8s kernel: Filesystem "dm-3": Disabling barriers, not
supported by the underlying device
Jan 8 17:38:06 linux-wh8s kernel: XFS mounting filesystem dm-3
Jan 8 17:38:06 linux-wh8s kernel: Ending clean XFS mount for filesystem: dm-3
Jan 8 17:38:08 linux-wh8s sudo: sigbj : TTY=tty1 ; PWD=/media/kontor/sigbj
; USER=root ; COMMAND=/usr/bin/Oppkoble_krypt_plater_og_pinner
Could I also have specified better the mkfs.xfs commandline too?
I just have done: mkfs.xfs /dev/hd..
I use LILO but forgot to bring the lilo.conf to you.
This machine setup is a preparation to go over to dmcryptLUKS with SLED 10 SP3.
OFF THE TOPIC:
The macine is an office machine designed for productionsystem, textfiles
mainly, written with vi/vim with special .vimrc configuration. Lots of
testprograms/scripts in bash and crontab running for daily, monthly and yearly
jobs. As previous mention - if you remember - sensitive personal info as to ID
specifications and confidential records.
The SLED 11 won't work on my printer, neither openSuSE 11.1 so I can't use
them, (driver problems - I have to use a HP Laserprint driver -).
I have used SuSE 7.3 up to date, and will not change before I am sure. I would
have to install SLED 10 SP3 on my home laptop too, to find out if things like
this will have to be changed:
From Eric Pements awk-script:
a = "\n\n\n\n\n\n\n" # L1-7 blank lines
a = a sprintf("%-18s %-41s %-16s\n", sp,$1,idNum) # L8 name, ID number
a = a "\n" # L9 blank
a = a sprintf("%-18s %-41s %-16s\n", sp,$2,$5) # L10 address, county
a = a "\n\n\n" # L11-13 blank
a = a sprintf("%-18s %-8s\n", sp,icpNum) # L14 ICP diagnosis
a = a "\n" # L15 blank
# L16 1, last, date1
a = a sprintf("%-20s 1 %7s %-32s %8.8s\n", sp,last,sp,date1)
a = a "\n\n\n\n" # L17-20 blank lines
Just to let you know.
---------------------------------------------------------------------
> ----- Original Message -----
> From: "Heinz Diehl" <htd@xxxxxxxxxxxxxxxxx>
> To: dm-crypt@xxxxxxxx
> Subject: Re: xfs and fstab
> Date: Thu, 7 Jan 2010 20:11:45 +0100
>
>
> On 07.01.2010, Si St wrote:
>
> > Here the main problem is XFS.
>
> I bet it's not.
>
> I have to machines running XFS (opensuse, set up manually) without any
> problems at all. Only /boot is ext2, all other partitions are XFS formatted.
>
> > Any wise brain here as to this matter?
>
> Please provide more information, e.g. your crypttab and menu.lst, and
> evtl. output of related logfiles.
>
> _______________________________________________
> dm-crypt mailing list
> dm-crypt@xxxxxxxx
> http://www.saout.de/mailman/listinfo/dm-crypt
>
--
_______________________________________________
Surf the Web in a faster, safer and easier way:
Download Opera 9 at http://www.opera.com
Powered by Outblaze
_______________________________________________
dm-crypt mailing list
dm-crypt@xxxxxxxx
http://www.saout.de/mailman/listinfo/dm-crypt
