From owner-freebsd-questions@FreeBSD.ORG Tue Dec 18 14:41:26 2012 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6E093F36 for ; Tue, 18 Dec 2012 14:41:26 +0000 (UTC) (envelope-from luke@bowbak.org) Received: from mail-ea0-f174.google.com (mail-ea0-f174.google.com [209.85.215.174]) by mx1.freebsd.org (Postfix) with ESMTP id E45078FC19 for ; Tue, 18 Dec 2012 14:41:25 +0000 (UTC) Received: by mail-ea0-f174.google.com with SMTP id e13so307440eaa.33 for ; Tue, 18 Dec 2012 06:41:19 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=PXhyz4r8DQYcUKr0Oo2Vb5nSEXFeeKJgaWGILFO2dlo=; b=myD7YEMDCIzE8GaWK+qC2+ckdwSJSHLHYRwbw4QaDX4oat1JNmhPR9Fmtn1w5wDOP6 1U0KQK26p0tDv+v+unwGJomh/EWeTuWr2qrWrPbM6oAK4S/hp69ARLgAhLXdvfQztTrO 1daM1bpM/eUDVfZAZq88UWrl0rl3khHikK2j6PK3MEXgyYblK938lyhB32R2uzmwlZ5F AughGQJPoasRyWqZHJTjgoYLPNEe45GhOvFkmKWm6UkWmm4GU8X2lBecPsesKP4ZbH+T uHi2kwYHTnxwiU2GJ0PyG2N4ViMrPUh3gNaZPk/NCZ9T/ok71EngxziWSiPRWhuC9FNX fcHA== MIME-Version: 1.0 Received: by 10.14.225.72 with SMTP id y48mr5924573eep.46.1355841331082; Tue, 18 Dec 2012 06:35:31 -0800 (PST) Received: by 10.14.118.80 with HTTP; Tue, 18 Dec 2012 06:35:30 -0800 (PST) X-Originating-IP: [67.168.115.71] In-Reply-To: <3EB59092-BFE2-4C5F-85A2-E225FBC3F5D9@fisglobal.com> References: <3EB59092-BFE2-4C5F-85A2-E225FBC3F5D9@fisglobal.com> Date: Tue, 18 Dec 2012 06:35:30 -0800 Message-ID: Subject: Re: FreeBSD as VMWare guest / disk resizing From: Luke Bakken To: Devin Teske Content-Type: text/plain; charset=ISO-8859-1 X-Gm-Message-State: ALoCoQkkNDo0XMElf+8pHq1FhwZGza1Gifv34IlzqEr5T9mjcu8DTPWfsZtjdC2B9eHm4gCO8COW Cc: freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Dec 2012 14:41:26 -0000 > You'll of course need to boot from another medium to do this. > That's my main question - can a larger disk be detected *without* a reboot. On FreeBSD instances running within VMWare I have been able to add new disks without a reboot but, as I described below, have not found a way to get the operating system to detect a larger *existing* disk without a reboot. VMWare allows you to resize a disk on the fly. Obviously I'm only interested in the "grow the disk" scenario :-) I'm beginning to think a reboot is necessary, which is surprising! > On Dec 17, 2012, at 4:15 PM, Luke Bakken wrote: > > Hello everyone - > > I'm looking for a way to get FreeBSD 8 / 9 to detect that an already > existing disk has grown. I have FreeBSD running as a guest within > vSphere ESX 5. Here is the output of camcontrol showing how the disks > are detected within the OS: > > [root@QA1HWFBSD83201 ~]# camcontrol inquiry da0 > pass0: Fixed Direct Access SCSI-2 device > pass0: 320.000MB/s transfers (160.000MHz, offset 127, 16bit), Command > Queueing Enabled > > In the VM settings I can increase the disk size but I can't seem to > find the right command within FreeBSD to force it to detect the new, > larger size without a reboot. 'camcontrol rescan all' works great to > detect a new drive but doesn't detect a larger disk. Within a Linux > distribution like Debian, the following command will detect the larger > drive: > > echo 1 > /sys/class/scsi_device/0:0:0:0/device/rescan > > I apologize if this has been answered in the archives or online but I > just haven't been able to get a definitive answer if this is possible, > and how. > > Thanks so much in advance, > Luke > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" > > > _____________ > The information contained in this message is proprietary and/or > confidential. If you are not the intended recipient, please: (i) delete the > message and all copies; (ii) do not disclose, distribute or use the message > in any manner; and (iii) notify the sender immediately. In addition, please > be aware that any message addressed to our domain is subject to archiving > and review by persons other than the intended recipient. Thank you.