toasters

toasters@lists.teaparty.net

3 participants
13514 discussions

Re: inconsistent mount attributes (ro/rw), RHEL5 / Netapp]
by Gregory Baker 19 Apr '07

19 Apr '07

It becomes more interesting (well, to me anyways) when you compare the behavior of RHEL3/4 (ro,rw netgroup export from filer works) with RHEL 5 (ro,rw netgroup export from filer no works). ---+ System environment [root@build-el3-64 greg]# uname -a Linux build-el3-64 2.4.21-47.ELsmp #1 SMP Wed Jul 5 20:30:30 EDT 2006 x86_64 unknown unknown GNU/Linux [root@build-el3-64 greg]# rpm -qa | grep nfs-utils nfs-utils-1.0.6-44EL [root@build-el3-64 mnt2]# mount -V mount: mount-2.11y ---+ NFS server (Netapp) environment [greg@apathy greg]$ sudo rsh eng version NetApp Release 7.2P4: Tue Nov 28 02:55:54 PST 2006 ---++ NFS export file entry [greg@apathy greg]$ sudo rsh eng exportfs | grep pandora /vol/vol4/pandora -sec=sys,ro,rw=@volexport-pandora,root=@volexport-pandora,anon=4058 ---++ netgroup member (for export file entry above) [root@build-el3-64 mnt2]# show_netgroup volexport-pandora | grep build-el3-64 build-el3-64.amd.com ---+ Demonstration of ro/rw mount reporting and working [root@build-el3-64 greg]# mount eng:/vol/vol4/pandora/pandora-k26_g25_64-2 /mnt2 [root@build-el3-64 greg]# mount -v | grep mnt2 eng:/vol/vol4/pandora/pandora-k26_g25_64-2 on /mnt2 type nfs (rw,addr=163.181.34 .137) [root@build-el3-64 greg]# cat /proc/mounts | grep mnt2 eng:/vol/vol4/pandora/pandora-k26_g25_64-2 /mnt2 nfs rw,v3,rsize=32768,wsize=327 68,hard,udp,lock,addr=eng 0 0 [root@build-el3-64 greg]# cd /mnt2 [root@build-el3-64 mnt2]# touch asdf [root@build-el3-64 mnt2]# ls -la asdf -rw-r--r-- 1 root root 0 Apr 19 13:18 asdf Ideas? Thanks, --Greg Choudhury, Bikash wrote: > There are two different things happening here. > > 1) The ro/rw rule in the filer exports file > > 2) The mount -v and cat/proc/mounts > > 1) Regarding the ro/rw rule that you have in the export file, I run a > small test in my lab. I have tried to replicate the problem with the > same rule as you have sent in your exports but I have not used the > netgroups instead used the ip subnets. I ran these tests on 7.2.2 filer. > > fas960c-svl04*> exportfs > > /vol/test_vol > -sec=sys,ro=172.17.39.0/22,rw=172.17.39.0/29,root=172.17.39.72,nosuid > > /vol/vol0/home -sec=sys,rw,nosuid > > /vol/vol0 -sec=sys,rw,anon=0,nosuid > > This is what you noticed on the Linux client: > > [root@ibmx335-svl14 mnt]# mount fas960c-svl04:/vol/test_vol /mnt/b1 > > [root@ibmx335-svl14 mnt]# ls -al > > total 20 > > drwxr-xr-x 3 root root 4096 Feb 28 03:12 . > > drwxr-xr-x 25 root root 4096 Feb 24 09:27 .. > > drwxr-xr-x 3 root root 4096 Nov 20 11:11 b1 > > [root@ibmx335-svl14 mnt]# cd /etc > > [root@ibmx335-svl14 etc]# touch /mnt/b1/testfile1 > > touch: cannot touch `/mnt/bik/testfile1': Permission denied > > On the filer I checked the permission for that file system. You can > probably run the same command on your filer to check the exact > permissions for /vol/vol4/Pandora. Replace the ip address with the one > for your RHEl5 client. > > fas960c-svl04*> exportfs -c 172.17.39.72 /vol/test_vol rw > > exportfs: 172.17.39.72 does not have rw access to /vol/test_vol (Access > reduced) > > fas960c-svl04*> exportfs -c 172.17.39.72 /vol/test_vol ro > > exportfs: 172.17.39.72 has ro access to /vol/test_vol > > > > This is definitely going to happen BECAUSE; take a look at the > /etc/exports file. The –ro is set on /22 subnet. This means 22 bits out > 32 are used as network address and the remaining 10 bits determine the > number of host i.e: 2^10. This indicates that the /22 with 255.255.252.0 > subnet has more number of clients that /29 with subnet 255.255.255.248. > When –ro is specified on a bigger network (/22) and –rw is listed with > the (/29) network, the more restricted one takes precedence, i.e ‘-ro’. > In my example the linux client had ip address 172.17.39.72 which falls > in the bigger network (/22) and is not in the (/29) network. Therefore > the client gets ‘-ro’ access instead of ‘rw’. When you try you a ‘touch’ > a file as ‘root’ from this client, you get ‘permission denied’ which is > legitimate because this client has ‘ro’ access. > > In your case you have -ro set on /vol/vol4/Pandora to every one and then > have -rw set to @volexport-pandora,root=@volexport-pandora which is part > of the wide spectrum that has '-ro' set. > > Then I switched the ‘ro’ to the (/29) network and ‘rw’ to (/22) network. > This is what it looks now. > > On the filer after the switch > > fas960c-svl04*> exportfs > > /vol/test_vol > -sec=sys,ro=172.17.39.0/29,rw=172.17.39.0/22,root=172.17.39.72,nosuid > > /vol/vol0/home -sec=sys,rw,nosuid > > /vol/vol0 -sec=sys,rw,anon=0,nosuid > > On the client after the switch: > > [root@ibmx335-svl14 etc]# touch /mnt/b1/testfile1 > > [root@ibmx335-svl14 etc]# ls -l /mnt/b1 > > total 0 > > -rw-r--r-- 1 root root 0 Feb 27 10:46 testfile1 > > > > fas960c-svl04*> exportfs -c 172.17.39.72 /vol/test_vol ro > > exportfs: 172.17.39.72 has ro access to /vol/test_vol > > fas960c-svl04*> exportfs -c 172.17.39.72 /vol/test_vol rw > > exportfs: 172.17.39.72 has rw access to /vol/test_vol > > > > Now I am able to touch the file w/o any problems. In your case > adcgar04.amd.com is part of the bigger network that has ‘ro’ access. As > suggested in the man page ‘ro’ will take precedence over ‘rw’ and > touching a file from a host in the /22 network will end up with a > ‘permission denied’. Currently this is by design. However, there is an > RFE 237892 open for this configuration to work. If you decide to upgrade > then you may consider 7.2.2 but this release does not fix this RFE. > > 2) I was currently running the above test from a RHEL5 client. But I did > not notice any difference in the mount options between 'mount -v' and > 'cat /proc/mounts'. > > [root@ibmx335-svl47 etc]# uname -a > > Linux ibmx335-svl47 2.6.18-8.el5 #1 SMP Fri Jan 26 14:15:21 EST 2007 > i686 i686 i386 GNU/Linux > > [root@ibmx335-svl47 ~]# rpm -qa |grep nfs-utils > > nfs-utils-1.0.9-16.el5 > > nfs-utils-lib-1.0.8-7.2 > > [root@ibmx335-svl47 ~]# mount -v|grep b1 > > 172.17.44.44:/vol/test_vol on /mnt/b1 type nfs4 > (*rw*,vers=4,rsize=65536,wsize=65536,hard,intr,proto=tcp,timeo=600,retrans=3,sec=sys,addr=172.17.44.44) > > [root@ibmx335-svl47 ~]# cat /proc/mounts|grep b1 > > 172.17.44.44:/vol/test_vol /mnt/b1 nfs4* > rw*,vers=4,rsize=65536,wsize=65536,hard,intr,proto=tcp,timeo=600,retrans=3,sec=sys,add > > Bikash R.Choudhury > > -----Original Message----- > From: Gregory Baker [mailto:gregory.baker@amd.com] > Sent: Wednesday, April 18, 2007 3:23 PM > To: toasters(a)mathworks.com > Cc: julia bauer > Subject: inconsistent mount attributes (ro/rw), RHEL5 / Netapp] > > Note I have cases open with Redhat and Netapp, but was curious if other > > people have also seen inconsistent mount attributes (ro/rw) when > > mounting RHEL5 client vs. Netapp 7.2 Ontap. > > ---+ System environment > > [greg@adcgar04 greg]$ uname -a > > Linux adcgar04 2.6.18-8.el5 #1 SMP Fri Jan 26 14:15:14 EST 2007 x86_64 > > unknown unknown GNU/Linux > > [greg@adcgar04 greg]$ rpm -qa | grep nfs-utils > > nfs-utils-1.0.9-16.el5 > > nfs-utils-lib-1.0.8-7.2 > > nfs-utils-lib-devel-1.0.8-7.2 > > nfs-utils-lib-1.0.8-7.2 > > nfs-utils-lib-devel-1.0.8-7.2 > > [greg@adcgar04 greg]$ mount -V > > mount (util-linux 2.13-pre7) > > ---+ NFS server (Netapp) environment > > [greg@apathy greg]$ sudo rsh eng version > > NetApp Release 7.2P4: Tue Nov 28 02:55:54 PST 2006 > > ---++ NFS export file entry > > [greg@apathy greg]$ sudo rsh eng exportfs | grep pandora > > /vol/vol4/pandora > > -sec=sys,ro,rw=@volexport-pandora,root=@volexport-pandora,anon=4058 > > ---++ netgroup member (for export file entry above) > > [greg@apathy greg]$ show_netgroup volexport-pandora | grep adcgar > > adcgar04.amd.com > > ---+ Demonstration of inconsistent ro/rw mount reporting > > [root@adcgar04 /]# mount eng:/vol/vol4/pandora/pandora-k26_g25_64-2 /mnt2 > > [root@adcgar04 /]# mount -v | grep mnt2 > > eng:/vol/vol4/pandora/pandora-k26_g25_64-2 on /mnt2 type nfs > > (rw,addr=163.181.34.137) > > [root@adcgar04 /]# cat /proc/mounts | grep mnt2 > > eng:/vol/vol4/pandora/pandora-k26_g25_64-2 /mnt2 nfs > > ro,vers=3,rsize=65536,wsize=65536,hard,intr,proto=tcp,timeo=600,retrans=2,sec=sys,addr=eng > > > 0 0 > > [root@adcgar04 /]# cd /mnt2/ > > [root@adcgar04 mnt2]# touch asdf > > touch: cannot touch `asdf': Read-only file system > > ---+ Discussion > > ---++Linux (RHEL3/4) NFS servers that have similiar exportfs options > > /tmp *(ro,anonuid=4058) @volexport-pandora(rw,no_root_squash) > > do not cause the inconsistent behavior between mount -v and /proc/mounts > > (and it is mounted rw as expected on the client). > > ---++ A reply from NetApp had this info: > > Starting with ONTAP 7.2.1 onward, ONTAP will display the "most > > pessimistic" permissions to NFSv3 and NFSv4 clients. NFSv2 clients will > > see permissions the same way as in previous releases of ONTAP, i.e. the > > "most optimistic" permissions. > > And mounting using NFS v2 (instead of v3) does give us the expected > > rw/rw consistency and ability. > > ---++ So now what? > > Should the linux mount -v and cat /proc/mounts be consistent with what > > is actually happening? > > Should netapp exports syntax handle a wildcard ro and a netgroup rw? > > Comments and feedback welcome. > > Thanks, > > --Greg > > -- > > ---------------------------------------------------------------------- > > Greg Baker 512-602-3287 (work) > > gregory.baker(a)amd.com 512-602-6970 (fax) > > 5204 E. Ben White Blvd MS 625 512-555-1212 (info) > > Austin, TX 78741 > > > > > ------------------------------------------------------------------------- > > This SF.net email is sponsored by DB2 Express > > Download DB2 Express C - the FREE version of DB2 express and take > > control of your XML. No limits. Just data. Click to get it now. > > http://sourceforge.net/powerbar/db2/ > > _______________________________________________ > > NFS maillist - NFS(a)lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/nfs > > > -- > > ---------------------------------------------------------------------- > > Greg Baker 512-602-3287 (work) > > gregory.baker(a)amd.com 512-602-6970 (fax) > > 5204 E. Ben White Blvd MS 625 512-555-1212 (info) > > Austin, TX 78741 > -- ---------------------------------------------------------------------- Greg Baker 512-602-3287 (work) gregory.baker(a)amd.com 512-602-6970 (fax) 5204 E. Ben White Blvd MS 625 512-555-1212 (info) Austin, TX 78741

1 0

inconsistent mount attributes (ro/rw), RHEL5 / Netapp]
by Gregory Baker 19 Apr '07

19 Apr '07

Note I have cases open with Redhat and Netapp, but was curious if other people have also seen inconsistent mount attributes (ro/rw) when mounting RHEL5 client vs. Netapp 7.2 Ontap. ---+ System environment [greg@adcgar04 greg]$ uname -a Linux adcgar04 2.6.18-8.el5 #1 SMP Fri Jan 26 14:15:14 EST 2007 x86_64 unknown unknown GNU/Linux [greg@adcgar04 greg]$ rpm -qa | grep nfs-utils nfs-utils-1.0.9-16.el5 nfs-utils-lib-1.0.8-7.2 nfs-utils-lib-devel-1.0.8-7.2 nfs-utils-lib-1.0.8-7.2 nfs-utils-lib-devel-1.0.8-7.2 [greg@adcgar04 greg]$ mount -V mount (util-linux 2.13-pre7) ---+ NFS server (Netapp) environment [greg@apathy greg]$ sudo rsh eng version NetApp Release 7.2P4: Tue Nov 28 02:55:54 PST 2006 ---++ NFS export file entry [greg@apathy greg]$ sudo rsh eng exportfs | grep pandora /vol/vol4/pandora -sec=sys,ro,rw=@volexport-pandora,root=@volexport-pandora,anon=4058 ---++ netgroup member (for export file entry above) [greg@apathy greg]$ show_netgroup volexport-pandora | grep adcgar adcgar04.amd.com ---+ Demonstration of inconsistent ro/rw mount reporting [root@adcgar04 /]# mount eng:/vol/vol4/pandora/pandora-k26_g25_64-2 /mnt2 [root@adcgar04 /]# mount -v | grep mnt2 eng:/vol/vol4/pandora/pandora-k26_g25_64-2 on /mnt2 type nfs (rw,addr=163.181.34.137) [root@adcgar04 /]# cat /proc/mounts | grep mnt2 eng:/vol/vol4/pandora/pandora-k26_g25_64-2 /mnt2 nfs ro,vers=3,rsize=65536,wsize=65536,hard,intr,proto=tcp,timeo=600,retrans=2,sec=sys,addr=eng 0 0 [root@adcgar04 /]# cd /mnt2/ [root@adcgar04 mnt2]# touch asdf touch: cannot touch `asdf': Read-only file system ---+ Discussion ---++Linux (RHEL3/4) NFS servers that have similiar exportfs options /tmp *(ro,anonuid=4058) @volexport-pandora(rw,no_root_squash) do not cause the inconsistent behavior between mount -v and /proc/mounts (and it is mounted rw as expected on the client). ---++ A reply from NetApp had this info: Starting with ONTAP 7.2.1 onward, ONTAP will display the "most pessimistic" permissions to NFSv3 and NFSv4 clients. NFSv2 clients will see permissions the same way as in previous releases of ONTAP, i.e. the "most optimistic" permissions. And mounting using NFS v2 (instead of v3) does give us the expected rw/rw consistency and ability. ---++ So now what? Should the linux mount -v and cat /proc/mounts be consistent with what is actually happening? Should netapp exports syntax handle a wildcard ro and a netgroup rw? Comments and feedback welcome. Thanks, --Greg -- ---------------------------------------------------------------------- Greg Baker 512-602-3287 (work) gregory.baker(a)amd.com 512-602-6970 (fax) 5204 E. Ben White Blvd MS 625 512-555-1212 (info) Austin, TX 78741 ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ NFS maillist - NFS(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs -- ---------------------------------------------------------------------- Greg Baker 512-602-3287 (work) gregory.baker(a)amd.com 512-602-6970 (fax) 5204 E. Ben White Blvd MS 625 512-555-1212 (info) Austin, TX 78741

2 1

RE: how to obtain patch releases
by Davin Milun 18 Apr '07

18 Apr '07

What's the feeling on 7.2.1.1P1, which is what I was about to deploy? Davin. At 13:47, on Mar 27, 2007, "Kevin Davis" wrote: > I'd stay away from 7.2.1P1 if I were you. We got slammed by _at least_ > 2 nasty bugs, and are now considering our options for applying > subsequent patches. (7.2.1.1D3, etc...) > > > > *------------------------------------------*-----------------------* > | Kevin Davis (UNIX Sysadmin) | Natick, Massachusetts | > | 508.647.7660 | 01760-2098 | > | mailto:kevin.davis@mathworks.com *-----------------------* > | http://www.mathworks.com | | > *------------------------------------------*-----------------------* > > > > > -----Original Message----- > > From: owner-toasters(a)mathworks.com > > [mailto:owner-toasters@mathworks.com] On Behalf Of J. Greg Mackinnon > > Sent: Monday, February 05, 2007 10:34 AM > > To: toasters > > Subject: how to obtain patch releases > > > > We currently are running OnTap 7.2.0 and not having fun with > > it. 7.2.1 contains many important fixes, but 7.2.1P1 has > > some critical fixes as well. I am getting fed up waiting for > > the next GA release, and I am willing to take the risk of > > running a patch build. The only problem... > > I cannot figure out how to download it! > > > > In the past I have found patch release download links in the > > NOW KB when referencing a related bug number... not so this time. > > > > Anyone know how to get the binaries? Open a support case? > > Bribe a NetApp tech? > > > > Thanks, > > -Greg Mackinnon > > University of Vermont

3 2

RE: Information on how Netapp single_image mode works
by Mike Ball 18 Apr '07

18 Apr '07

Thanks for the responses but I am still confused about how the paths are determined. For example, lets say I have a FAS6030C (Node1 and Node2) running Data Ontap 7.2.1 with each head having 2 target ports each in a switched fibre fabric. In this fabric, I have a Windows host (running Snapdrive 4.2.1 and DSM 3.0) with a dual port fibre card. I create lun0 on Node1 from the Windows host via Snapdrive. How is the path chosen by the FAS6030C? Is there a round robin algorithm which gives out the target port on Node1 to the Windows host? -----Original Message----- From: Paul Rosham [mailto:paulrosham@yahoo.com.au] Sent: Monday, April 16, 2007 11:26 PM To: 'Jack Lyons'; 'Nils Vogels' Cc: Mike Ball; toasters(a)mathworks.com Subject: RE: Information on how Netapp single_image mode works In addition, anything with a reasonable NVRAM/Cluster interconnect setup (i.e. 3000, 6000 series) the additional latency of the request passing to the correct head via the cluster interconect is almost negligible. -----Original Message----- From: owner-toasters(a)mathworks.com [mailto:owner-toasters@mathworks.com] On Behalf Of Jack Lyons Sent: Tuesday, 17 April 2007 11:10 AM To: Nils Vogels Cc: Mike Ball; toasters(a)mathworks.com Subject: Re: Information on how Netapp single_image mode works one caveat, based on my experience the host based software will see all paths to the filer as equal, so if you hit the WWPN on the "other" head of the cluster, you will get an error message and an ASUP. It is annoying, and as far as I know, not a problem. Jack Nils Vogels wrote: > Hey Mike, > > On 4/16/07, Mike Ball <MBall(a)datalink.com> wrote: >> >> I am trying to find additional information on how Netapp single_image >> mode works in a clustered environment as it pertains to pathing. >> Single_image mode pulls all the WWPN's from the Netapp cluster and >> presents it to the SAN as one WWNN. What I would like to know is how >> paths are determined from hosts to cluster nodes if no target portals >> are defined? >> > > There will be multiple paths available (at least 2, one for ClusterA, > one for ClusterB) and you generally will need host-based path > selection software to select the active one. > > Some software selects on 'Most Recently Used', other selects on fixed > path, this may vary per multipathing-software. >

6 8

Information on how Netapp single_image mode works
by Mike Ball 17 Apr '07

17 Apr '07

I am trying to find additional information on how Netapp single_image mode works in a clustered environment as it pertains to pathing. Single_image mode pulls all the WWPN's from the Netapp cluster and presents it to the SAN as one WWNN. What I would like to know is how paths are determined from hosts to cluster nodes if no target portals are defined?

3 2

ndmpcopy and the newb
by Brian Dunbar 16 Apr '07

16 Apr '07

Hi, I'm new to managing Filers - I hope you'll put up with a newb question or two while I get on my feet. I've not been left entirely on my own here - but there are two unix guys here to mange a lot of servers where before there were four of us .. and the two guys who had done this job previously are the ones who left for greener pastures. So I've got a mature and reasonably stable infrastructue to work with at least. My first task is to move a volume from a busy filer to a non-busy filer. 1. The preferred method (for our shop, I'm told) is to use ndmpcopy I've got shell access to both filers, they can ping each other. I've got a desination volume created. ndmpcopy [options] source destination The source and destination specify a hostname (no problem) and aboslute pathname of the directory to be used for the transfer. Does this mean the absolute pathname of the source/destination volume? Or .. something else? If the former how do I find that? 2. Unless there is a better way to do this? I can of course mount both volumes via NFS from a 3rd host and simply move then but (from what I've read) ndmpcoy is a better choice. Brian Dunbar Plexus brian.dunbar(a)plexus.com

8 10

5um or 90um
by Willeke, Jochen 16 Apr '07

16 Apr '07

Hi toasters, does anybody know if we can use 9um LC-LC cables to connect a shelf with an ESH2 to a filer, or are 50um LC-LC cables the only supported ones? Because this will be a production system i need to know if it is covered from Netapp-support. Sadly i did not find anything about this on NOW. Best Regards and thanks in advance Jochen

4 4

Replacing an FAS960 with a 3070
by Matt Phelps 13 Apr '07

13 Apr '07

All, We'll be replacing a 960 with a new 3070 soon and am wondering if anyone's gone through this upgrade path yet. Our current plan is to install 7.2.2 for the 3070 (which is an x86_64 based OS) with the 960 still up, run "download" to put the boot stuff on the disks, then edit the /etc/rc file to change the device names for the network interface, then shutdown and swap the heads. Hopefully the 3070 will just come up and hum right along. Any gotchyas? -- Matt Phelps System Administrator, Computation Facility Harvard - Smithsonian Center for Astrophysics mphelps(a)cfa.harvard.edu, http://cfa-www.harvard.edu

6 6

RE: How to create a new filer
by Holloway, Chris 13 Apr '07

13 Apr '07

You could try booting into Maintenance mode (ctrl+c during startup) and then selecting option 4a which is "initialize all disks and create a flexible root volume" or something similar (assuming it's ONTAP 7). Once this is done it will boot into ONTAP but this is not a full version, so you just need to do an ONTAP "upgrade" to it to get all the right files on there. Your config and licenses will be lost so you'll need to re-enter them. Chris -------------------------------------------------------- Christopher Holloway Consultant Professional Services Main: +44 (0)1423 519000 Direct: +44 (0)1423 519099 Fax: +44 (0)1423 519251 Mobile: DNS Arrow Nidderdale House Beckwith Knowle Harrogate HG3 1SA www.DNSarrow.co.uk Email Confidentiality Notice: This message is private and confidential. If you have received this message in error, please notify us and remove it from your system. "DNS Arrow" means Digital Network Services (UK) Limited, a company registered in England. Company Registration Number 3952678. Registered Office: Squire, Sanders & Dempsey, Level 28 Tower 42, 25 Old Broad Street, London EC2N 1HQ, UK. ________________________________ From: owner-toasters(a)mathworks.com [mailto:owner-toasters@mathworks.com] On Behalf Of Davies,Matt Sent: 13 April 2007 14:23 To: toasters(a)mathworks.com Subject: How to create a new filer Hi all, Having just changed out our FAS250's for FAS270's, and utilised the old 250 as a shelf on the 270. I have been left with the processor and licenses for a FAS250. The question is, if I buy a DS14Mk2 shelf full of disks, and put the processor in the new shelf, how would I get this to become a filer once again as there will be no Root volume Does anyone know all the steps involved, or can someone point me in the right direction ? Thanks Matt ____________________________________________________________ This e-mail (including all attachments) is confidential and may be privileged. It is for the exclusive use of the addressee only. If you are not the addressee, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please erase all copies of the message and its attachments and notify us immediately at help(a)generalatlantic.com. Thank You.

2 1

How to create a new filer
by Davies,Matt 13 Apr '07

13 Apr '07

Hi all, Having just changed out our FAS250's for FAS270's, and utilised the old 250 as a shelf on the 270. I have been left with the processor and licenses for a FAS250. The question is, if I buy a DS14Mk2 shelf full of disks, and put the processor in the new shelf, how would I get this to become a filer once again as there will be no Root volume Does anyone know all the steps involved, or can someone point me in the right direction ? Thanks Matt _____________________________________________________________ This e-mail (including all attachments) is confidential and may be privileged. It is for the exclusive use of the addressee only. If you are not the addressee, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please erase all copies of the message and its attachments and notify us immediately at help(a)generalatlantic.com <mailto:help@generalatlantic.com>. Thank You.

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

1997

toasters