From mboxrd@z Thu Jan 1 00:00:00 1970 To: 9fans@cse.psu.edu Subject: Re: [9fans] add new disk drives to fs. From: forsyth@vitanuova.com MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="upas-svkbxpkqgcyylpajizrvtvdgxh" Message-Id: <20010423120319.4BE0B19AEA@mail.cse.psu.edu> Date: Mon, 23 Apr 2001 13:03:48 +0100 Topicbox-Message-UUID: 8ba6a9c0-eac9-11e9-9e20-41e7f4b1d025 This is a multi-part message in MIME format. --upas-svkbxpkqgcyylpajizrvtvdgxh Content-Disposition: inline Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit i normally do something like this, which might be less work, and doesn't require an intermediate copy of the file system (unless you'd like the backup, which you might). i was going to send this privately but i'll post it to the list in case i've slipped up somewhere. add the new discs to the file server, leaving the original one as well, being sure to use distinct SCSI IDs. create a new file system on the new devices, initialise it and set allow mode filsys newfs [w2w3] # or whatever your configuration is for the new devices ream newfs # be very careful to ream the right name! allow now you've got access to both the original main and empty newfs file systems at the same time from the cpu server or terminals. copy from one to another, preserving permissions and ownership # mount existing file system on /n/boot so as to avoid copying files in /net and /dev(!) 9fs boot # mount the destination file system on /n/tapefs (or some other name) mount -c /srv/boot /n/tapefs newfs # note the `newfs' argument to select other than `main' you can do some test file creations, writes and removals on /n/tapefs. # copy the files, preserving permissions disk/mkfs -a -s /n/boot /lib/proto/allproto | disk/mkext -u -d /n/tapefs in this last command, again be sure that /n/boot looks right and /n/tapefs was correctly mounted from the file server, and that you've typed it in correctly (and that what i gave you makes sense), because you're in allow mode without a safety net. then `halt' the file server, remove the old disc and enter config mode. i'll use the same scsi IDs as above but with the old device out you could renumber with appropriate changes. config w2 # or whatever is appropriate # re-enter your ip ipmask ipgw and service name filsys main [w2w3] end --upas-svkbxpkqgcyylpajizrvtvdgxh Content-Type: message/rfc822 Content-Disposition: inline Return-Path: <9fans-admin@cse.psu.edu> Received: from punt-1.mail.demon.net by mailstore for forsyth@vitanuova.com id 988013682:10:06238:4; Mon, 23 Apr 2001 08:14:42 GMT Received: from psuvax1.cse.psu.edu ([130.203.4.6]) by punt-1.mail.demon.net id aa1004220; 23 Apr 2001 8:13 GMT Received: from psuvax1.cse.psu.edu (psuvax1.cse.psu.edu [130.203.30.6]) by mail.cse.psu.edu (CSE Mail Server) with ESMTP id 99043199FF; Mon, 23 Apr 2001 04:13:12 -0400 (EDT) Received: from ginnan.cc.titech.ac.jp (ginnan.cc.titech.ac.jp [131.112.14.2]) by mail.cse.psu.edu (CSE Mail Server) with SMTP id 2075A199E9 for <9fans@cse.psu.edu>; Mon, 23 Apr 2001 04:12:51 -0400 (EDT) Received: (qmail 20393 invoked from network); 23 Apr 2001 08:12:46 -0000 Received: from beat.cc.titech.ac.jp (131.112.4.22) by ginnan.cc.titech.ac.jp with SMTP; 23 Apr 2001 08:12:46 -0000 Received: (qmail 27800 invoked from network); 23 Apr 2001 08:12:46 -0000 Received: from localhost (HELO beat.cc.titech.ac.jp) (127.0.0.1) by localhost with SMTP; 23 Apr 2001 08:12:46 -0000 To: cse.psu.edu!9fans Mime-Version: 1.0 (generated by tm-edit 7.106) Content-Type: text/plain; charset=US-ASCII Message-ID: <27798.988013565@beat.cc.titech.ac.jp> Subject: [9fans] add new disk drives to fs. Sender: cse.psu.edu!9fans-admin Errors-To: 9fans-admin@cse.psu.edu X-BeenThere: 9fans@cse.psu.edu X-Mailman-Version: 2.0.1 Precedence: bulk Reply-To: cse.psu.edu!9fans List-Id: Fans of the OS Plan 9 from Bell Labs <9fans.cse.psu.edu> List-Archive: Date: Mon, 23 Apr 2001 17:12:45 +0900 I live on a file server with a 2GB SCSI disk reamed by `filsys main w0'. Having got new disk drives, I want to add these to the `main'. my imagined steps: 1: boot a cpu/auth server from a local disk. 2: mount the fs on /n/myfs. 3: `wrap/create' the above /n/myfs to some remote ftpfs filesystem. 4: `filsys' and `ream' the fs with new disks 5: `wrap/inst' the `wrap/create'd the /n/myfs to the fs's / Do you think the above steps will do? I want advise about permission and date issue that may concern in the step 3 especially. Thank you. -- YAMANASHI Takeshi. --upas-svkbxpkqgcyylpajizrvtvdgxh--