SEO

Hello everybody,

while setting up and testing a QFS 4.1 shared filesystem (DAU size 16k)
on two nodes (one V440 and one V480, both Solaris 9, connected via
Brokade Silkworm 3200 to a 3510 storage, latest QFS 4.1 patch installed,
but not with EIS-CD patched, md data disk) which is mounted on
/export/home I encountered following problem:

On the metadata server I untared the openssh sources into the QFS.
Then I did a ./configure and afterwards a make. The make exited
with errors because it sayed 'unterminated comment in <some c-file1>.c'.
When I looked into <some c-file1>.c I saw that it discontinued in the
middle of the file. Then I removed the openssh source directory and
untared it again into the QFS. This time it worked. But I did the
same thing again and now the make stopped at <some c-file2>.c whith
the same symptoms, the file was discontinued. I did this several times
and sometimes it worked and sometimes it didn't.
To shorten this a bit, here are my further observations:

1. on the host which is not metadata server it works without any
problems, even when I untar openssh on the metadata server and then
compile it on the host which is not the metadata server. Even when I
untar the openssh sources on the host which is not the metadata server
and then compile it on the metadata server it works

2. Observation from point 1 is not machine dependent, when I switch the
metadata server over to the other server, compilation fails there and on
the other it works.

3. when I untar the openssh tarfile and do a cp -r openssh-3.9p1 /tmp
and then issue a ./configure; make (in the qfs directory of course) it
works, even on the metadata server

4. when I untar it and do a diff over all files with the ones from /tmp/
(which are all correct) there are no differences and when I issue
the ./configure; make (in the qfs directory), after the diff,it works,
even on the metadata server

5. when I unmount and mount the filesystem and try my tar; ./configure;
make sequence it fails with a chanch of 100%

6. On QFS 4.0 everything works fine

7. I had a disk which is greater than 1 TB at the beginning as data
disk, after segmenting it to 2 smaller disks (2 x 750GB, I thought
of a bug in connexion with the EFI label or the new support for large
disks in 4.1) the behavior is still the same

8. I tried the forcedirectio mount option, without any success

9. The problem occurs with SAM-QFS 4.1 and QFS 4.1

10. With a data disk size / QFS size of only 10G it fails too

11. With equipment identifier mr it works

12. With QFS/SAM-QFS 4.1 single reader/writer everything works fine

13. With DAU size 32k or 64k (with shared filesystem) everything works
fine (even with the big 1,5TB disk and EFI labeled)

Here is my mcf:
qfshomedirs 1 ma qfshomedirs on shared
/dev/dsk/c2t216000C0FF803518d2s0 10 mm qfshomedirs on
/dev/dsk/c2t216000C0FF803518d1s0 20 md qfshomedirs on
/dev/dsk/c2t216000C0FF803518d3s0 30 md qfshomedirs on

I have no defaults.conf or other configuration files.
The mount options in /etc/vfstab are stripe=0,shared

Do any of you have some idea of what I could have done wrong or perhaps
seen the same behavior like I?

By the way, do any of you know how to remove a EFI label from a disk?
Since I can only access the slices of the disks and not the whole disk
via the /dev/ directory I don't know how to overwrite the first 34 blocks.

Many thanks in advance.

Stefan Peinkofer