Thanks for this hint, I haven't thought on this fact, thats excactly what is going on here:

View over NFS:

## 1st File ls -l /mnt/mcad_vault/Singapore_Dev_Loc_xml/CAD_New_1_CAApData.xml -rw-rw-rw- 1 6500 6500 2540 Jul 19 2007 /mnt/mcad_vault/Singapore_Dev_Loc_xml/CAD_New_1_CAApData.xml

## 2nd File ls -l /mnt/mcad_vault/Singapore_Dev_Loc_xml/CAD_NEW_1_CAApData.xml -rw-rw-rw- 1 6500 6500 4136 Jul 20 2007 /mnt/mcad_vault/Singapore_Dev_Loc_xml/CAD_NEW_1_CAApData.xml

View over CIFS:

## 1st File ls -l /mnt1/mcad_vault/Singapore_Dev_Loc_xml/CAD_New_1_CAApData.xml -rwxr-xr-x 1 root root 2540 Jul 19 2007 /mnt1/mcad_vault/Singapore_Dev_Loc_xml/CAD_New_1_CAApData.xml

## 2nd File ls -l /mnt1/mcad_vault/Singapore_Dev_Loc_xml/CAD_NEW_1_CAApData.xml -rwxr-xr-x 1 root root 2540 Jul 19 2007 /mnt1/mcad_vault/Singapore_Dev_Loc_xml/CAD_NEW_1_CAApData.xml

CIFS doesn't see a difference as NFS does. Very nice "Ahhhh" effect, thanks!

-----Original Message----- From: Stephen C. Losen [mailto:scl@sasha.acc.Virginia.EDU] Sent: Friday, May 30, 2008 3:09 PM To: Buerger, Andreas Cc: toasters@mathworks.com Subject: Re: Different view of the same file from win & linux

Hi,

We are experiencing a strange issue on one of our r200 systems. We have a volume, which is accessed from linux and windows. There is no issue with rights etc, the problem is that there are a few files, that have been created some time ago, have different versions

and

a different content, just from the OS that you are looking from.

I tracked this user issue on my admin host (SuSe 9.3 2.6.11.4-20a-default): (The original host is running on Solaris, both the problem occurs on every host) I mounted the volume twice, via NFS & CIFS.

SMB Mount: //nstore2/pdmmig$ on /mnt1 type smbfs (0)

NFS Mount: nstore2:/vol/pdmmig on /mnt type nfs (rw,addr=172.18.131.211)

This is one of the files that are affected by this strange issue:

ls -l /mnt1/mcad_vault/Singapore_Dev_Loc_xml/CAD_NEW_1_CAApData.xml -rwxr-xr-x 1 root root 2540 Jul 19 2007 /mnt1/mcad_vault/Singapore_Dev_Loc_xml/CAD_NEW_1_CAApData.xml

ls -l /mnt/mcad_vault/Singapore_Dev_Loc_xml/CAD_NEW_1_CAApData.xml -rw-rw-rw- 1 6500 6500 4136 Jul 20 2007 /mnt/mcad_vault/Singapore_Dev_Loc_xml/CAD_NEW_1_CAApData.xml

A diff on both files, proves the difference that is already indicated

by

the file size. There is no difference between the two paths, both

mounts

point to the same path and to the same file, but there is a difference in the content between them. I've already tested a little bit with caching, links etc, but this doesn't seem to point in the right way. Additionally it's not possible for me, to reproduce the problem with

new

files.

Do you have any ideas?

Regards Andreas

Could it be the capitalization of the file names? Windows file names are case insensitive, while on Linux they are case sensitive. (Actually, Windows preserves capitalization when storing file names, but searches for file names case insensitively.)

On Windows if you create a file called "AAA" and then later on "save to" a file named "aaa" then file "AAA" gets overwritten. Basically, Windows does not allow you to create two different files whose names differ only by capitalization.

On Unix systems such as Linux however, you can create two separate files such as AAA and aaa. Both of these files are visible on Unix. I don't recall if both files appear in folder listings on Windows (via CIFS) but I do know that if you reference "aaa" or "AAA" you always get the same file due to the case insensitive search. One of the two files cannot be accessed from Windows (CIFS) no matter which name you use.

Perhaps that is what you are seeing. NFS uses Unix file name rules while CIFS (SMB) uses Windows. On NFS look for file names that differ just by capitalization. These will cause problems when accessed via CIFS.

Steve Losen scl@virginia.edu phone: 434-924-0640

University of Virginia ITC Unix Support

I would suspect that you would have to create a new one, mount it, and copy the contents from the original.

----- Original Message ----- From: "Suresh Rajagopalan" SRajagopalan@williamoneil.com To: toasters@mathworks.com Sent: Friday, May 30, 2008 2:15 PM Subject: Resize lun more than 10x

Hi,

I am running up against the 10x limit to resize a lun. How do I copy the lun to one with a larger size?

Thanks Suresh

What is this resize limit you are talking about? I didn't know about any restrictions.

Cheers, André

When you first create a LUN its "geometry" is set based on the initial size. By geometry I mean the number of heads, number of cylinders, sectors/cylinder, bytes/sector (pseudo values required by SCSI.) When you enlarge a LUN, some (but not all) of these values can be increased and eventually you hit a limit. (Perhaps you can only grow LUNs in units of cylinders -- not sure) So if you create a 1 GB LUN, then its geometry is constrained by this small size. Later on if you try to grow the LUN to over 1 TB then you will need to increase a geometry parameter (cylinders?) beyond the SCSI limit. Had you created a 500G LUN to begin with, the initial geometry would have been different and it would be able to grow to 1 TB. This is all rather silly because a LUN on a netapp doesn't actually have a geometry. This is an artifact of the SCSI protocol, which specifies disk blocks by head, cylinder, and sector.

-----Ursprüngliche Nachricht----- Von: owner-toasters@mathworks.com [mailto:owner-toasters@mathworks.com] Im Auftrag von Bill Holland Gesendet: Freitag, 30. Mai 2008 23:21 An: Suresh Rajagopalan; toasters@mathworks.com Betreff: Re: Resize lun more than 10x

I would suspect that you would have to create a new one, mount it, and copy the contents from the original.

----- Original Message ----- From: "Suresh Rajagopalan" SRajagopalan@williamoneil.com To: toasters@mathworks.com Sent: Friday, May 30, 2008 2:15 PM Subject: Resize lun more than 10x

...

Hi,

I am running up against the 10x limit to resize a lun. How do I copy the lun to one with a larger size?

Thanks Suresh

Steve Losen scl@virginia.edu phone: 434-924-0640

University of Virginia ITC Unix Support