Re: question on crypt xlator

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hello Emmanuel,

Thanks for the report,
I am still not sure that symlinks are the culprit.
Could you please try the attached version of crypt.t and report results?

Thank you,
Edward.


On Fri, 10 Oct 2014 20:10:08 +0200
manu@xxxxxxxxxx (Emmanuel Dreyfus) wrote:

> Edward Shishkin <edward@xxxxxxxxxx> wrote:
> 
> > Could you please replace the file ./tests/encryption/crypt.t
> > with the attached one, run the last one, and report about results?
> 
> It had errors with busy device at umount time, but I replaced the two
> umount by this (like everywhere else in the test suite) and it passed
> the test with success:
> EXPECT_WITHIN $UMOUNT_TIMEOUT "Y" force_umount $M0
> 

#!/bin/bash

. $(dirname $0)/../include.rc
. $(dirname $0)/../volume.rc

cleanup;

TEST glusterd
TEST pidof glusterd

## Create a volume with one brick
TEST $CLI volume create $V0 $H0:$B0/${V0}1;
EXPECT "$V0" volinfo_field $V0 'Volume Name';
EXPECT 'Created' volinfo_field $V0 'Status';
EXPECT '1' brick_count $V0

## Turn off performance translators

TEST $CLI volume set $V0 performance.quick-read off
EXPECT 'off' volinfo_field $V0 'performance.quick-read'
TEST $CLI volume set $V0 performance.write-behind off
EXPECT 'off' volinfo_field $V0 'performance.write-behind'
TEST $CLI volume set $V0 performance.open-behind off
EXPECT 'off' volinfo_field $V0 'performance.open-behind'

## Turn on crypt xlator by setting features.encryption to on
TEST $CLI volume set $V0 encryption on
EXPECT 'on' volinfo_field $V0 'features.encryption'

## Specify location of master key
TEST $CLI volume set $V0 encryption.master-key /tmp/$V0-master-key

## Create a file with master key

echo "0000111122223333444455556666777788889999aaaabbbbccccddddeeeeffff" > /tmp/$V0-master-key

## Start the volume
TEST $CLI volume start $V0;
EXPECT 'Started' volinfo_field $V0 'Status';

## Mount the volume
TEST $GFS --volfile-server=$H0 --volfile-id=$V0 $M0;

## Testing writev, readv, ftruncate:
## Create fragmented files and compare them with the reference files

build_tester $(dirname $0)/frag.c
TEST $(dirname $0)/frag $M0/testfile /tmp/$V0-goodfile 262144 500

## access the fragmented file after remount
EXPECT_WITHIN $UMOUNT_TIMEOUT "Y" force_umount $M0
TEST glusterfs --volfile-server=$H0 --volfile-id=$V0 $M0;

EXPECT "" diff -u $M0/testfile /tmp/$V0-goodfile

## Testing link, unlink, symlink, rename

#create link, rename, create symlink
TEST ln $M0/testfile $M0/testfile-link
TEST mv $M0/testfile $M0/testfile-renamed
TEST ln -s $M0/testfile-link $M0/testfile-symlink

#access link, renamed file and symlink after remount
EXPECT_WITHIN $UMOUNT_TIMEOUT "Y" force_umount $M0
TEST glusterfs --volfile-server=$H0 --volfile-id=$V0 $M0;

EXPECT "" diff -u $M0/testfile-link /tmp/$V0-goodfile
EXPECT "" diff -u $M0/testfile-renamed /tmp/$V0-goodfile
EXPECT "" diff -u $M0/testfile-symlink /tmp/$V0-goodfile

TEST rm -f $M0/testfile-link
TEST rm -f $M0/testfile-renamed
TEST rm -f $M0/testfile-symlink

## Cleanup files

TEST rm -f /tmp/$V0-master-key
TEST rm -f /tmp/$V0-goodfile

EXPECT_WITHIN $UMOUNT_TIMEOUT "Y" force_umount $M0

## Reset crypt options
TEST $CLI volume reset $V0 encryption.block-size
TEST $CLI volume reset $V0 encryption.data-key-size

## Stop the volume
TEST $CLI volume stop $V0;
EXPECT 'Stopped' volinfo_field $V0 'Status';

## Delete the volume
TEST $CLI volume delete $V0;
TEST ! $CLI volume info $V0;

TEST rm -rf $(dirname $0)/frag
cleanup;
_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxxx
http://supercolony.gluster.org/mailman/listinfo/gluster-devel

[Index of Archives]     [Gluster Users]     [Ceph Users]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux