toasters

toasters@lists.teaparty.net

3 participants
13514 discussions

RE: Max number of drives.
by Alvarado, Michael 08 Oct '99

08 Oct '99

This also applies to the F630. It is 1.39 TB to be exact. -----Original Message----- From: tkaczma(a)gryf.net [mailto:tkaczma@gryf.net] Sent: Thursday, October 07, 1999 5:13 PM To: toasters(a)mathworks.com Subject: RE: Max number of drives. On Thu, 7 Oct 1999, Alvarado, Michael wrote: > Yes you look at the maximum storage capacity the OS supports. In the case of > the F760, it is 1.4TB. What about an F630 running the same OS? Tom

1 0

Re: File locking, sendmail and toasters
by alexei＠mindspring.net 08 Oct '99

08 Oct '99

Nick Hilliard <nick(a)iol.ie> writes: > If you need to have text-based NFS-mounted client mailboxes, the only > reliable option is to use a mailbox format which doesn't require locking, > such as Maildir. Depending on what access is provided to the mail spool, yes, maildir is a safer, viable format. Check procmail for to use as an LDA for this or look a qmail for some other thoughts on how this is done. But not all instances can work with this. If you have shell users that do funky stuff based on the mbox format, this can be a problem. There are plenty of other cases where maildir is not a viable alternative to mbox. I hope you find what you need. Alex

3 2

What Radius servers are recommended to work with the Netcache Appliance?
by Mike Ball 08 Oct '99

08 Oct '99

What Radius servers are recommended or have been tested with the Netcache appliance? Mike Ball Open System Solutions, Inc. 3124 Spring Forest Rd Raleigh, NC 27616 Fax: 919-871-6308 Vmail: 919-871-6301 ext. 311 Email: mball(a)opensystems.com Http: www.opensystems.com

1 0

open bugs / closed bugs
by Jay Soffian 08 Oct '99

08 Oct '99

In searching for a bug on NOW, I've noticed that a majority of bugs are still in the open state. Does this mean these bugs have not been fixed? What does the 'release fix' column refer to? Does this mean the bug applies only to that specific release, or that the bug was fixed in that release, or that the bug was first noticed in that release? Are bugs numbered in a strictly sequential order? If so, how is it that bug #289 applies to release 5.3? It would be nice to see the bug tracking system be setup more clearly, perhaps with the following fields: Date bug opened. Date bug closed. First release bug noticed. Releases which contain bug. First release which fixed bug. State: (opened, analyzed, solved, fix incorporated into release). I'd have to guess that the NOW bug system is not the same system used internally by NA engineers. j. -- Jay Soffian <jay(a)cimedia.com> UNIX Systems Engineer 404.572.1941 Cox Interactive Media

1 0

RE: Max number of drives.
by Alvarado, Michael 08 Oct '99

08 Oct '99

Yes you look at the maximum storage capacity the OS supports. In the case of the F760, it is 1.4TB. -----Original Message----- From: Jason Middlebrooks [mailto:Jason_Middlebrooks@datalink.com] Sent: Thursday, October 07, 1999 1:37 PM To: Thompson, Arnold Cc: Mohler, Jeff; toasters(a)mathworks.com Subject: RE: Max number of drives. I am not concerned about mixing the drives in the volume because like drive will be in there own raidgroup. I am just wondering about the max number of drives. All the docs say 28 18Gig drives and 56 9Gig drives in a loop. But what if you have 21 18Gig drives and 14 9Gig drives? Do you look at the maximum Storage Capacity to determine how many total drive you can have when you mix them? Thanks Jason "Thompson, Arnold" <arnold.thompson(a)netapp.com> on 10/07/99 03:46:34 PM To: "Mohler, Jeff" <jeff.mohler(a)netapp.com>, Jason Middlebrooks/Datalink, toasters(a)mathworks.com cc: Subject: RE: Max number of drives. I recall from mixing 9s and 18s at a customer site that you *can* add the 18s to an existing volume of 9s and still get 18G worth (minus filesystem overhead, snaps, etc.) from each 18G drive. The first 18G drive becomes parity and the 9G parity becomes a data drive (so you get 9G additional capacity from the first 18G drive), but after that you should get 18 and not 9. Historically, you've been able to mix and match with the filer doing the right thing. It is true that if a 9G drive fails and there is no 9G spare, it will rebuild on an 18G drive but you will only get 9G on that rebuilt drive. So be sure to have a spare of each size available. If anybody has tested this with different results I could be completely nuts, so please educate us! It is important to make the 9G shelves the lowest order shelves for FCAL loop initialization purposes, so make the 9G shelves numbers 0 and 1. Regards, Arnie > -----Original Message----- > From: Mohler, Jeff [mailto:jeff.mohler@netapp.com] > Sent: Thursday, October 07, 1999 11:38 AM > To: 'Jason Middlebrooks'; toasters(a)mathworks.com > Subject: RE: Max number of drives. > > > Sure, no problem. > > But when you add them to a volume (if you are not creating a > new one) make sure > you add them to the volume made up of 18G drives. (That is, > if the 18G drives > are a separate volume from the 9G ones). > > If you mix/max drive sizes in a volume, the larger drives > will appear only to be > the size of the smallest drive in the array. > > -----Original Message----- > From: Jason Middlebrooks [mailto:Jason_Middlebrooks@datalink.com] > Sent: Thursday, October 07, 1999 12:01 PM > To: toasters(a)mathworks.com > Subject: Max number of drives. > > > Question. > > I have 14 9Gig drives and 14 18Gig drives. So a total of 28 > drives. Can I > add 7 more 18Gig drives on the same loop? > > The filer is a F760 > > Thanks in advance > Jason Middlebrooks >

2 1

RE: Max number of drives.
by Palinckx, Gregory 08 Oct '99

08 Oct '99

Hi Jason, There is a 56 drive hardware limit per FC-AL loop. There is also a total capacity software restriction. I believe this is a F760, so the software restriction will be about 1.4TB. Greg > -----Original Message----- > From: Jason Middlebrooks [mailto:Jason_Middlebrooks@datalink.com] > Sent: Thursday, October 07, 1999 2:37 PM > To: Thompson, Arnold > Cc: Mohler, Jeff; toasters(a)mathworks.com > Subject: RE: Max number of drives. > > > I am not concerned about mixing the drives in the volume > because like drive > will be in there own raidgroup. I am just wondering about > the max number > of drives. All the docs say 28 18Gig drives and 56 9Gig > drives in a loop. > But what if you have 21 18Gig drives and 14 9Gig drives? Do > you look at > the maximum Storage Capacity to determine how many total > drive you can have > when you mix them? > > Thanks > Jason > > > > > > "Thompson, Arnold" <arnold.thompson(a)netapp.com> on 10/07/99 > 03:46:34 PM > > To: "Mohler, Jeff" <jeff.mohler(a)netapp.com>, Jason > Middlebrooks/Datalink, > toasters(a)mathworks.com > cc: > Subject: RE: Max number of drives. > > > > > I recall from mixing 9s and 18s at a customer site that you > *can* add the > 18s to > an existing volume of 9s and still get 18G worth (minus filesystem > overhead, > snaps, etc.) from each 18G drive. The first 18G drive > becomes parity and > the 9G > parity becomes a data drive (so you get 9G additional > capacity from the > first > 18G drive), but after that you should get 18 and not 9. Historically, > you've > been able to mix and match with the filer doing the right > thing. It is > true > that if a 9G drive fails and there is no 9G spare, it will > rebuild on an > 18G > drive but you will only get 9G on that rebuilt drive. So be > sure to have a > spare of each size available. If anybody has tested this > with different > results > I could be completely nuts, so please educate us! > > It is important to make the 9G shelves the lowest order > shelves for FCAL > loop > initialization purposes, so make the 9G shelves numbers 0 and 1. > > Regards, > Arnie > > > > -----Original Message----- > > From: Mohler, Jeff [mailto:jeff.mohler@netapp.com] > > Sent: Thursday, October 07, 1999 11:38 AM > > To: 'Jason Middlebrooks'; toasters(a)mathworks.com > > Subject: RE: Max number of drives. > > > > > > Sure, no problem. > > > > But when you add them to a volume (if you are not creating a > > new one) make sure > > you add them to the volume made up of 18G drives. (That is, > > if the 18G drives > > are a separate volume from the 9G ones). > > > > If you mix/max drive sizes in a volume, the larger drives > > will appear only to be > > the size of the smallest drive in the array. > > > > -----Original Message----- > > From: Jason Middlebrooks [mailto:Jason_Middlebrooks@datalink.com] > > Sent: Thursday, October 07, 1999 12:01 PM > > To: toasters(a)mathworks.com > > Subject: Max number of drives. > > > > > > Question. > > > > I have 14 9Gig drives and 14 18Gig drives. So a total of 28 > > drives. Can I > > add 7 more 18Gig drives on the same loop? > > > > The filer is a F760 > > > > Thanks in advance > > Jason Middlebrooks > > > > >

2 1

RE: Max number of drives.
by Jason Middlebrooks 07 Oct '99

07 Oct '99

I am not concerned about mixing the drives in the volume because like drive will be in there own raidgroup. I am just wondering about the max number of drives. All the docs say 28 18Gig drives and 56 9Gig drives in a loop. But what if you have 21 18Gig drives and 14 9Gig drives? Do you look at the maximum Storage Capacity to determine how many total drive you can have when you mix them? Thanks Jason "Thompson, Arnold" <arnold.thompson(a)netapp.com> on 10/07/99 03:46:34 PM To: "Mohler, Jeff" <jeff.mohler(a)netapp.com>, Jason Middlebrooks/Datalink, toasters(a)mathworks.com cc: Subject: RE: Max number of drives. I recall from mixing 9s and 18s at a customer site that you *can* add the 18s to an existing volume of 9s and still get 18G worth (minus filesystem overhead, snaps, etc.) from each 18G drive. The first 18G drive becomes parity and the 9G parity becomes a data drive (so you get 9G additional capacity from the first 18G drive), but after that you should get 18 and not 9. Historically, you've been able to mix and match with the filer doing the right thing. It is true that if a 9G drive fails and there is no 9G spare, it will rebuild on an 18G drive but you will only get 9G on that rebuilt drive. So be sure to have a spare of each size available. If anybody has tested this with different results I could be completely nuts, so please educate us! It is important to make the 9G shelves the lowest order shelves for FCAL loop initialization purposes, so make the 9G shelves numbers 0 and 1. Regards, Arnie > -----Original Message----- > From: Mohler, Jeff [mailto:jeff.mohler@netapp.com] > Sent: Thursday, October 07, 1999 11:38 AM > To: 'Jason Middlebrooks'; toasters(a)mathworks.com > Subject: RE: Max number of drives. > > > Sure, no problem. > > But when you add them to a volume (if you are not creating a > new one) make sure > you add them to the volume made up of 18G drives. (That is, > if the 18G drives > are a separate volume from the 9G ones). > > If you mix/max drive sizes in a volume, the larger drives > will appear only to be > the size of the smallest drive in the array. > > -----Original Message----- > From: Jason Middlebrooks [mailto:Jason_Middlebrooks@datalink.com] > Sent: Thursday, October 07, 1999 12:01 PM > To: toasters(a)mathworks.com > Subject: Max number of drives. > > > Question. > > I have 14 9Gig drives and 14 18Gig drives. So a total of 28 > drives. Can I > add 7 more 18Gig drives on the same loop? > > The filer is a F760 > > Thanks in advance > Jason Middlebrooks >

1 0

RE: Max number of drives.
by Palinckx, Gregory 07 Oct '99

07 Oct '99

Hi All - Unless something has changed in the 5.3 days, Arnie is correct - you can add 18s to a 9GB group and get 18(17)GB. Here is a sysconfig from a customer out here - RAID group 0 RAID Disk HA.ID HA SHELF BAY CHAN Used (MB/blks) Phys (MB/blks) --------- ----- ------------ ---- -------------- -------------- parity 0a.11 0a 1 3 FC:A 17000/34816000 17366/35566480 data 0a.5 0a 0 5 FC:A 8600/17612800 8683/17783112 data 0a.1 0a 0 1 FC:A 8600/17612800 8683/17783112 data 0a.2 0a 0 2 FC:A 8600/17612800 8683/17783112 data 0a.3 0a 0 3 FC:A 8600/17612800 8683/17783112 data 0a.6 0a 0 6 FC:A 8600/17612800 8683/17783112 data 0a.4 0a 0 4 FC:A 8600/17612800 8683/17783112 data 0a.13 0a 1 5 FC:A 17000/34816000 17366/35566480 data 0a.12 0a 1 4 FC:A 17000/34816000 17366/35566480 data 0a.9 0a 1 1 FC:A 17000/34816000 17366/35566480 I would just be sure that you have enough 18s to get a decent stripe.... Greg SE - Rockies > -----Original Message----- > From: Mohler, Jeff [mailto:jeff.mohler@netapp.com] > Sent: Thursday, October 07, 1999 1:50 PM > To: Thompson, Arnold; 'Jason Middlebrooks'; 'toasters(a)mathworks.com' > Subject: RE: Max number of drives. > > > Im scratching some documents here.. > > I could have swore the last time I asked that I was told the > larger drives would > be counted as the smaller capacity drives after the parity drive. > > > > -----Original Message----- > From: Thompson, Arnold > Sent: Thursday, October 07, 1999 12:47 PM > To: Mohler, Jeff; 'Jason Middlebrooks'; toasters(a)mathworks.com > Subject: RE: Max number of drives. > > > I recall from mixing 9s and 18s at a customer site that you > *can* add the 18s to > an existing volume of 9s and still get 18G worth (minus > filesystem overhead, > snaps, etc.) from each 18G drive. The first 18G drive > becomes parity and the 9G > parity becomes a data drive (so you get 9G additional > capacity from the first > 18G drive), but after that you should get 18 and not 9. > Historically, you've > been able to mix and match with the filer doing the right > thing. It is true > that if a 9G drive fails and there is no 9G spare, it will > rebuild on an 18G > drive but you will only get 9G on that rebuilt drive. So be > sure to have a > spare of each size available. If anybody has tested this > with different results > I could be completely nuts, so please educate us! > > It is important to make the 9G shelves the lowest order > shelves for FCAL loop > initialization purposes, so make the 9G shelves numbers 0 and 1. > > Regards, > Arnie > > > > -----Original Message----- > > From: Mohler, Jeff [mailto:jeff.mohler@netapp.com] > > Sent: Thursday, October 07, 1999 11:38 AM > > To: 'Jason Middlebrooks'; toasters(a)mathworks.com > > Subject: RE: Max number of drives. > > > > > > Sure, no problem. > > > > But when you add them to a volume (if you are not creating a > > new one) make sure > > you add them to the volume made up of 18G drives. (That is, > > if the 18G drives > > are a separate volume from the 9G ones). > > > > If you mix/max drive sizes in a volume, the larger drives > > will appear only to be > > the size of the smallest drive in the array. > > > > -----Original Message----- > > From: Jason Middlebrooks [mailto:Jason_Middlebrooks@datalink.com] > > Sent: Thursday, October 07, 1999 12:01 PM > > To: toasters(a)mathworks.com > > Subject: Max number of drives. > > > > > > Question. > > > > I have 14 9Gig drives and 14 18Gig drives. So a total of 28 > > drives. Can I > > add 7 more 18Gig drives on the same loop? > > > > The filer is a F760 > > > > Thanks in advance > > Jason Middlebrooks > > >

1 0

RE: Max number of drives.
by Mohler, Jeff 07 Oct '99

07 Oct '99

Im scratching some documents here.. I could have swore the last time I asked that I was told the larger drives would be counted as the smaller capacity drives after the parity drive. -----Original Message----- From: Thompson, Arnold Sent: Thursday, October 07, 1999 12:47 PM To: Mohler, Jeff; 'Jason Middlebrooks'; toasters(a)mathworks.com Subject: RE: Max number of drives. I recall from mixing 9s and 18s at a customer site that you *can* add the 18s to an existing volume of 9s and still get 18G worth (minus filesystem overhead, snaps, etc.) from each 18G drive. The first 18G drive becomes parity and the 9G parity becomes a data drive (so you get 9G additional capacity from the first 18G drive), but after that you should get 18 and not 9. Historically, you've been able to mix and match with the filer doing the right thing. It is true that if a 9G drive fails and there is no 9G spare, it will rebuild on an 18G drive but you will only get 9G on that rebuilt drive. So be sure to have a spare of each size available. If anybody has tested this with different results I could be completely nuts, so please educate us! It is important to make the 9G shelves the lowest order shelves for FCAL loop initialization purposes, so make the 9G shelves numbers 0 and 1. Regards, Arnie > -----Original Message----- > From: Mohler, Jeff [mailto:jeff.mohler@netapp.com] > Sent: Thursday, October 07, 1999 11:38 AM > To: 'Jason Middlebrooks'; toasters(a)mathworks.com > Subject: RE: Max number of drives. > > > Sure, no problem. > > But when you add them to a volume (if you are not creating a > new one) make sure > you add them to the volume made up of 18G drives. (That is, > if the 18G drives > are a separate volume from the 9G ones). > > If you mix/max drive sizes in a volume, the larger drives > will appear only to be > the size of the smallest drive in the array. > > -----Original Message----- > From: Jason Middlebrooks [mailto:Jason_Middlebrooks@datalink.com] > Sent: Thursday, October 07, 1999 12:01 PM > To: toasters(a)mathworks.com > Subject: Max number of drives. > > > Question. > > I have 14 9Gig drives and 14 18Gig drives. So a total of 28 > drives. Can I > add 7 more 18Gig drives on the same loop? > > The filer is a F760 > > Thanks in advance > Jason Middlebrooks >

1 0

RE: Max number of drives.
by Thompson, Arnold 07 Oct '99

07 Oct '99

I recall from mixing 9s and 18s at a customer site that you *can* add the 18s to an existing volume of 9s and still get 18G worth (minus filesystem overhead, snaps, etc.) from each 18G drive. The first 18G drive becomes parity and the 9G parity becomes a data drive (so you get 9G additional capacity from the first 18G drive), but after that you should get 18 and not 9. Historically, you've been able to mix and match with the filer doing the right thing. It is true that if a 9G drive fails and there is no 9G spare, it will rebuild on an 18G drive but you will only get 9G on that rebuilt drive. So be sure to have a spare of each size available. If anybody has tested this with different results I could be completely nuts, so please educate us! It is important to make the 9G shelves the lowest order shelves for FCAL loop initialization purposes, so make the 9G shelves numbers 0 and 1. Regards, Arnie > -----Original Message----- > From: Mohler, Jeff [mailto:jeff.mohler@netapp.com] > Sent: Thursday, October 07, 1999 11:38 AM > To: 'Jason Middlebrooks'; toasters(a)mathworks.com > Subject: RE: Max number of drives. > > > Sure, no problem. > > But when you add them to a volume (if you are not creating a > new one) make sure > you add them to the volume made up of 18G drives. (That is, > if the 18G drives > are a separate volume from the 9G ones). > > If you mix/max drive sizes in a volume, the larger drives > will appear only to be > the size of the smallest drive in the array. > > -----Original Message----- > From: Jason Middlebrooks [mailto:Jason_Middlebrooks@datalink.com] > Sent: Thursday, October 07, 1999 12:01 PM > To: toasters(a)mathworks.com > Subject: Max number of drives. > > > Question. > > I have 14 9Gig drives and 14 18Gig drives. So a total of 28 > drives. Can I > add 7 more 18Gig drives on the same loop? > > The filer is a F760 > > Thanks in advance > Jason Middlebrooks >

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