root file system not mounted, some children mounted

Moderators: jhartley, MSR734, nola

root file system not mounted, some children mounted

Post by grahamperrin » Fri Oct 26, 2012 1:24 am

A highlight from http://www.wuala.com/grahamperrin/publi ... de=gallery

Image

  • root file system tall was no longer mounted
  • some of its children remained mounted
  • Finder view of volumes at the Computer level appeared wrong.

The symptom was noticeable a few minutes after concurrent backups using a slightly modified version of zfstimemachinebackup.perl

  • a send from pool zhandy
  • a send from pool gjp22
  • both received in pool tall

First noticeable probably after I:

  1. successfully ejected all volumes of zhandy
  2. aimed to eject all volumes of tall.

It's not unusual for the OS to continue signalling that a volume (disk) was not ejected – long after eject. Here, screenshots show those dialogues for root file system tall and for a child, backups.

It's extremely rare to find a disorderly sequence of unmounts, where child file systems are present. I might have seen the behaviour only once before.

Environment

  • OS X 10.8.2
  • ZEVO Community Edition 1.1.1
  • relatively little free space in the destination pool.

Additional details available on request.

Postscript

It's possible that neither tall nor backups was mounted before the sends began – I vaguely recall wondering why they were missing (from the Finder view of Computer) shortly after connecting the disk … but I can't recall whether that was around the time of this particular incident.

More on this in a separate topic: sometimes, not all volumes at the Computer level in Finder
grahamperrin Offline

User avatar
 
Posts: 1596
Joined: Fri Sep 14, 2012 10:21 pm
Location: Brighton and Hove, United Kingdom

Return to General Discussion

Who is online

Users browsing this forum: ilovezfs and 2 guests

cron