mount(2) man page lists the following reasons for it to return an EBUSY: EBUSY source is already mounted. Or, it cannot be remounted read-only, because it still holds files open for writing. Or, it cannot be mounted on target because target is still busy (it is the working directory of some task, the mount point of another device, has open files, etc.). Or, it could not be unmounted because it is busy.
Tina Soles wrote: > P.S., I also executed the following, and get the same results for UUID > and ls -l on both nodes: > > #echo "stats" | debugfs.ocfs2 -n /dev/sdb1 > Revision: 0.90 > Mount Count: 0 Max Mount Count: 20 > State: 0 Errors: 0 > Check Interval: 0 Last Check: Sun Jun 29 16:33:16 2008 > Creator OS: 0 > Feature Compat: 1 BackupSuper > Feature Incompat: 16 Sparse > Tunefs Incomplete: 0 None > Feature RO compat: 0 None > Root Blknum: 17 System Dir Blknum: 18 > First Cluster Group Blknum: 8 > Block Size Bits: 12 Cluster Size Bits: 15 > Max Node Slots: 4 > Label: oradatafiles > UUID: 43CB1E6A5E4D465CAFC11A3C22BDC851 > Inode: 2 Mode: 00 Generation: 2444960055 (0x91bb2137) > FS Generation: 2444960055 (0x91bb2137) > Type: Unknown Attr: 0x0 Flags: Valid System Superblock > User: 0 (root) Group: 0 (root) Size: 0 > Links: 0 Clusters: 15262000 > ctime: 0x4867f18c -- Sun Jun 29 16:33:16 2008 > atime: 0x0 -- Wed Dec 31 19:00:00 1969 > mtime: 0x4867f18c -- Sun Jun 29 16:33:16 2008 > dtime: 0x0 -- Wed Dec 31 19:00:00 1969 > ctime_nsec: 0x00000000 -- 0 > atime_nsec: 0x00000000 -- 0 > mtime_nsec: 0x00000000 -- 0 > Last Extblk: 0 > Sub Alloc Slot: Global Sub Alloc Bit: 65535 > > > echo "ls -l /" | debugfs.ocfs2 -n /dev/sdb1 > 17 drwxr-xr-x 3 0 0 4096 > 29-Jun-2008 1 > 6:33 . > 17 drwxr-xr-x 3 0 0 4096 > 29-Jun-2008 1 > 6:33 .. > 258057 drwxr-xr-x 2 0 0 4096 > 29-Jun-2008 1 > 6:34 lost+found > > -----Original Message----- > From: Tina Soles > Sent: Monday, June 30, 2008 6:39 AM > To: '[EMAIL PROTECTED]'; Tao Ma > Cc: ocfs2-users@oss.oracle.com > Subject: RE: [Ocfs2-users] Problems building ocfs2 rpm on Fedora 9 > > OK, so I mounted the disk from node 1, using: > > mount -t ocfs2 -o nointr /dev/sdb1 /ocfs2/oradata/orcl > > works great: > > #mount > /dev/mapper/VolGroup00-LogVol00 on / type ext3 (rw) > proc on /proc type proc (rw) > sysfs on /sys type sysfs (rw) > devpts on /dev/pts type devpts (rw,gid=5,mode=620) > /dev/sda1 on /boot type ext3 (rw) > tmpfs on /dev/shm type tmpfs (rw) > none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw) > sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw) > fusectl on /sys/fs/fuse/connections type fusectl (rw) > gvfs-fuse-daemon on /root/.gvfs type fuse.gvfs-fuse-daemon > (rw,nosuid,nodev) > configfs on /sys/kernel/config type configfs (rw) > ocfs2_dlmfs on /dlm type ocfs2_dlmfs (rw) > /dev/sdb1 on /ocfs2/oradata/orcl type ocfs2 > (rw,_netdev,nointr,heartbeat=local) > > however, trying to execute the same command from node 2 results in the > following: > > mount -t ocfs2 -o nointr /dev/sdb1 /ocfs2/oradata/orcl > mount.ocfs2: Device or resource busy while mounting /dev/sdb1 on > /ocfs2/oradata/orcl. Check 'dmesg' for more information on this error. > > dmesg on node 1 shows: > > ocfs2: Mounting device (8,17) on (node 0, slot 0) with ordered data > mode. > o2net: accepted connection from node slingshot.strsoftware.com (num 1) > at 192.168.0.28:7777 > o2net: no longer connected to node slingshot.strsoftware.com (num 1) at > 192.168.0.28:7777 > > dmesg on node 2 shows: > > EXT3 FS on sdb1, internal journal > EXT3-fs: mounted filesystem with ordered data mode. > OCFS2 Node Manager 1.5.0 > OCFS2 DLM 1.5.0 > OCFS2 DLMFS 1.5.0 > OCFS2 User DLM kernel interface loaded > OCFS2 Node Manager 1.5.0 > OCFS2 DLM 1.5.0 > OCFS2 DLMFS 1.5.0 > OCFS2 User DLM kernel interface loaded > o2net: connected to node skydive.strsoftware.com (num 0) at > 192.168.0.27:7777 > OCFS2 1.5.0 > o2net: no longer connected to node skydive.strsoftware.com (num 0) at > 192.168.0.27:7777 > > Do I have something configured incorrectly, or do I need an additional > option in my mount command? > > Thanks.... > > > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: Sunday, June 29, 2008 11:20 PM > To: Tao Ma; Tina Soles > Cc: ocfs2-users@oss.oracle.com > Subject: Re: [Ocfs2-users] Problems building ocfs2 rpm on Fedora 9 > > datavolume mount option is only on ocfs2 for enterprise kernels. > > For most part, you shouldn't require it for using it as a datastore. > Instead set init.ora param filesystemio_options to directio (or is it > odirect). > > The only bit that won't work here is using ocfs2 for the voting disk and > ocr... as datavolume is necessary to force enable odirect. > But you can always use raw for that. > > Sunil > > _______________________________________________ > Ocfs2-users mailing list > Ocfs2-users@oss.oracle.com > http://oss.oracle.com/mailman/listinfo/ocfs2-users > _______________________________________________ Ocfs2-users mailing list Ocfs2-users@oss.oracle.com http://oss.oracle.com/mailman/listinfo/ocfs2-users
