From: Jeff Sipek <jeffpc@optonline.net>
To: Hielke Christian Braun <hcb@unco.de>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.0-test1 cryptoloop & aes & xfs
Date: Mon, 21 Jul 2003 13:12:32 -0400 [thread overview]
Message-ID: <200307211312.40068.jeffpc@optonline.net> (raw)
In-Reply-To: <20030720213803.GA777@jolla>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Sunday 20 July 2003 17:38, Hielke Christian Braun wrote:
> Thanks for the tip. With util-linux-2.12 i can setup the device.
>
> So the new cryptoloop in 2.6.0 is incompatible to the one in the
> international crypto patch?
>
> I could not access my old data. So i created a new one. But when
> i copy some data onto it, i get:
>
> XFS mounting filesystem loop5
> Ending clean XFS mount for filesystem: loop5
> xfs_force_shutdown(loop5,0x8) called from line 1070 of file
> fs/xfs/xfs_trans.c. Return address = 0xc02071ab Filesystem "loop5":
> Corruption of in-memory data detected. Shutting down filesystem: loop5
> Please umount the filesystem, and rectify the problem(s)
>
> To setup, i did this:
>
> losetup -e aes /dev/loop5 /dev/hda4
> mkfs.xfs /dev/hda4
No, you should use
mkfs.xfs /dev/loop5
you want to create a fs on the loop device.
Jeff.
- --
bad pun of the week: the formula 1 control computer suffered from a race
condition
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
iD8DBQE/HB8EwFP0+seVj/4RAn6DAJ9pqcYxLq2mee/RaFCBdtr3YvorlgCgkubm
IY3V6WaA0K3xNnIqL0yNIQU=
=2FAW
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2003-07-21 17:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-20 0:57 2.6.0-test1 cryptoloop & aes Hielke Christian Braun
2003-07-20 8:38 ` Andries Brouwer
2003-07-20 21:38 ` 2.6.0-test1 cryptoloop & aes & xfs Hielke Christian Braun
2003-07-20 22:15 ` Andries Brouwer
2003-07-21 17:12 ` Jeff Sipek [this message]
2003-07-22 0:24 ` Hielke Christian Braun
2003-07-22 11:54 ` Jari Ruusu
2003-07-29 23:28 ` 2.6.0-test1 cryptoloop & aes Bill Davidsen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200307211312.40068.jeffpc@optonline.net \
--to=jeffpc@optonline.net \
--cc=hcb@unco.de \
--cc=linux-kernel@vger.kernel.org \
--subject='Re: 2.6.0-test1 cryptoloop & aes & xfs' \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).