-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Fri, 28 Aug 2009, Gabriel VLASIU wrote: > I receive this error then I try to mount a encrypted loop-AES partition: > > loop0: loop_end_io_transfer err=-95 bi_rw=0x5 > > For all others encrypted partitions I do not receive this error. Can be > ignored? It is safe to stick for now with this kernel? > > kernel: 2.6.18-164.el5_3g.AES (RHEL 5.4 beta, compiled from sources at: > http://people.redhat.com/dzickus/el5/164.el5/src/kernel-2.6.18-164.el5.src.rpm) > loop-AES: 3.2g OK, I thing I know why this error occur. I use loop0 to mount a partition on top of raid5 array (software). File-system is xfs. When partition is about to be mounted kernel xfs module want to enable barriers and fail and continue with barriers disabled. If I mount the partition with an explicit "nobarrier" option, the error is gone. # losetup -F /dev/loo0 <--- no error reported # mount /dev/loop0 /mnt/qwer <--- error reported # mount -o barrier /dev/loop0 /mnt/qwer <--- error reported # mount -o nobarrier /dev/loop0 /mnt/qwer <--- no error reported All other partitions are "normal" ones and barrier can be enabled for them (well, at least with this kernel - I've seen the same behavior in 2.6.30 from Fedora but not in the previous ones). Of course, it would be nice to have no error reported... Gabriel - -- // Gabriel VLASIU // // OpenGPG-KeyID : 0xE684206E // OpenGPG-Fingerprint: 0C3D 9F8B 725D E243 CB3C 8428 796A DB1F E684 206E // OpenGPG-URL : http://www.vlasiu.net/public.key -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFKmEmNeWrbH+aEIG4RAoHbAJ9RvNqdLtAfFxPkAZrz7oCCRQ99xACePqJO lfEg+i4yWuFkzUvO8MK5g70= =SaKM -----END PGP SIGNATURE----- - Linux-crypto: cryptography in and on the Linux system Archive: http://mail.nl.linux.org/linux-crypto/
