Zpool upgrade on this system went fine, but zfs upgrade failed:
# zfs upgrade -a
cannot unmount ''/space/direct'': Device busy
cannot unmount ''/space/dcc'': Device busy
cannot unmount ''/space/direct'': Device busy
cannot unmount ''/space/imap'': Device busy
cannot unmount ''/space/log'': Device busy
cannot unmount ''/space/mysql'': Device busy
2 filesystems upgraded
Do I have to shut down all the applications before upgrading the
filesystems? This is on a Solaris 10 5/09 system.
--
-Gary Mills- -Unix Group- -Computer and Network Services-
Hi Gary, This should just work without having to do anything. Looks like a bug but I haven''t seen this problem before. Anything unusual about the mount points for the file systems identified below? Thanks, Cindy On 07/29/10 07:07, Gary Mills wrote:> Zpool upgrade on this system went fine, but zfs upgrade failed: > > # zfs upgrade -a > cannot unmount ''/space/direct'': Device busy > cannot unmount ''/space/dcc'': Device busy > cannot unmount ''/space/direct'': Device busy > cannot unmount ''/space/imap'': Device busy > cannot unmount ''/space/log'': Device busy > cannot unmount ''/space/mysql'': Device busy > 2 filesystems upgraded > > Do I have to shut down all the applications before upgrading the > filesystems? This is on a Solaris 10 5/09 system. >
Hi Gary, I found a similar zfs upgrade failure with the device busy error, which I believe was caused by a file system mounted under another file system. If this is the cause, I will file a bug or find an existing one. The workaround is to unmount the nested file systems and upgrade them individually, like this: # zfs upgrade space/direct # zfs upgrade space/dcc Thanks, Cindy On 07/29/10 09:48, Cindy Swearingen wrote:> Hi Gary, > > This should just work without having to do anything. > > Looks like a bug but I haven''t seen this problem before. > > Anything unusual about the mount points for the file systems > identified below? > > Thanks, > > Cindy > > On 07/29/10 07:07, Gary Mills wrote: >> Zpool upgrade on this system went fine, but zfs upgrade failed: >> >> # zfs upgrade -a >> cannot unmount ''/space/direct'': Device busy >> cannot unmount ''/space/dcc'': Device busy >> cannot unmount ''/space/direct'': Device busy >> cannot unmount ''/space/imap'': Device busy >> cannot unmount ''/space/log'': Device busy >> cannot unmount ''/space/mysql'': Device busy >> 2 filesystems upgraded >> >> Do I have to shut down all the applications before upgrading the >> filesystems? This is on a Solaris 10 5/09 system. >> > _______________________________________________ > zfs-discuss mailing list > zfs-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
On Thu, Jul 29, 2010 at 12:00:08PM -0600, Cindy Swearingen wrote:> Hi Gary, > > I found a similar zfs upgrade failure with the device busy error, which > I believe was caused by a file system mounted under another file system. > > If this is the cause, I will file a bug or find an existing one. > > The workaround is to unmount the nested file systems and upgrade them > individually, like this: > > # zfs upgrade space/direct > # zfs upgrade space/dcc''zfs upgrade'' unmounts file system first, which makes it hard to upgrade for example root file system. The only work-around I found is to clone root file system (clone is created with most recent version), change root file system to newly created clone, reboot, upgrade original root file system, change root file system back, reboot, destroy clone. -- Pawel Jakub Dawidek http://www.wheelsystems.com pjd at FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 196 bytes Desc: not available URL: <http://mail.opensolaris.org/pipermail/zfs-discuss/attachments/20100729/5deeb8dc/attachment.bin>
On Thu, Jul 29, 2010 at 10:26:14PM +0200, Pawel Jakub Dawidek wrote:> On Thu, Jul 29, 2010 at 12:00:08PM -0600, Cindy Swearingen wrote: > > > > I found a similar zfs upgrade failure with the device busy error, which > > I believe was caused by a file system mounted under another file system. > > > > If this is the cause, I will file a bug or find an existing one.No, it was caused by processes active on those filesystems.> > The workaround is to unmount the nested file systems and upgrade them > > individually, like this: > > > > # zfs upgrade space/direct > > # zfs upgrade space/dccExcept that I couldn''t unmount them because the filesystems were busy.> ''zfs upgrade'' unmounts file system first, which makes it hard to upgrade > for example root file system. The only work-around I found is to clone > root file system (clone is created with most recent version), change > root file system to newly created clone, reboot, upgrade original root > file system, change root file system back, reboot, destroy clone.In this case it wasn''t the root filesystem, but I still had to disable twelve services before doing the upgrade and enable them afterwards. `fuser -c'' is useful to identify the processes. Mapping them to services can be difficult. The server is essentially down during the upgrade. For a root filesystem, you might have to boot off the failsafe archive or a DVD and import the filesystem in order to upgrade it. -- -Gary Mills- -Unix Group- -Computer and Network Services-
Hi Gary, I will file a bug to track the zfs upgrade/device busy problem. We use beadm or lucreate to upgrade the root BE so we generally don''t have to do an in-place root dataset replacement. Thanks, Cindy On 07/29/10 17:03, Gary Mills wrote:> On Thu, Jul 29, 2010 at 10:26:14PM +0200, Pawel Jakub Dawidek wrote: >> On Thu, Jul 29, 2010 at 12:00:08PM -0600, Cindy Swearingen wrote: >>> I found a similar zfs upgrade failure with the device busy error, which >>> I believe was caused by a file system mounted under another file system. >>> >>> If this is the cause, I will file a bug or find an existing one. > > No, it was caused by processes active on those filesystems. > >>> The workaround is to unmount the nested file systems and upgrade them >>> individually, like this: >>> >>> # zfs upgrade space/direct >>> # zfs upgrade space/dcc > > Except that I couldn''t unmount them because the filesystems were busy. > >> ''zfs upgrade'' unmounts file system first, which makes it hard to upgrade >> for example root file system. The only work-around I found is to clone >> root file system (clone is created with most recent version), change >> root file system to newly created clone, reboot, upgrade original root >> file system, change root file system back, reboot, destroy clone. > > In this case it wasn''t the root filesystem, but I still had to disable > twelve services before doing the upgrade and enable them afterwards. > `fuser -c'' is useful to identify the processes. Mapping them to > services can be difficult. The server is essentially down during the > upgrade. > > For a root filesystem, you might have to boot off the failsafe archive > or a DVD and import the filesystem in order to upgrade it. >