archive mirror
 help / color / mirror / Atom feed
From: Jeff Sipek <>
To: Hielke Christian Braun <>,
Subject: Re: 2.6.0-test1 cryptoloop & aes & xfs
Date: Mon, 21 Jul 2003 13:12:32 -0400	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <20030720213803.GA777@jolla>

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.


- -- 
bad pun of the week: the formula 1 control computer suffered from a race 
Version: GnuPG v1.2.2 (GNU/Linux)


  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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).