Wow that was mighty quick Tim!
Sorry, I have to reboot the server. I can SSH into the box, VNC etc but no CIFS
shares are visible.
Here are the last few messages from /var/adm/messages
Nov 20 23:48:55 sta-nas-01 pcplusmp: [ID 805372 kern.info] pcplusmp: ide (ata)
instance 0 irq 0xe vector 0x41 ioapic 0x2 intin 0xe is bound to cpu 0
Nov 20 23:48:55 sta-nas-01 pcplusmp: [ID 805372 kern.info] pcplusmp: ide (ata)
instance 1 irq 0xf vector 0x41 ioapic 0x2 intin 0xf is bound to cpu 1
Nov 20 23:48:55 sta-nas-01 pcplusmp: [ID 805372 kern.info] pcplusmp: ide (ata)
instance 0 irq 0xe vector 0x41 ioapic 0x2 intin 0xe is bound to cpu 0
Nov 20 23:48:55 sta-nas-01 pcplusmp: [ID 805372 kern.info] pcplusmp: ide (ata)
instance 1 irq 0xf vector 0x41 ioapic 0x2 intin 0xf is bound to cpu 1
Nov 20 23:48:55 sta-nas-01 pcplusmp: [ID 805372 kern.info] pcplusmp: ide (ata)
instance 0 irq 0xe vector 0x41 ioapic 0x2 intin 0xe is bound to cpu 0
Nov 20 23:48:55 sta-nas-01 pcplusmp: [ID 805372 kern.info] pcplusmp: ide (ata)
instance 1 irq 0xf vector 0x41 ioapic 0x2 intin 0xf is bound to cpu 1
Nov 20 23:48:55 sta-nas-01 smbd[552]: [ID 413393 daemon.error] dyndns: failed
to get domainname
Nov 20 23:50:44 sta-nas-01 last message repeated 4 times
Nov 20 23:50:45 sta-nas-01 zoneadmd[2329]: [ID 702911 daemon.error] [zone
'tomcat01'] WARNING: e1000g3:1: no matching subnet found in netmasks(4):
192.168.0.122; using default of 255.255.255.0.
Nov 20 23:50:45 sta-nas-01 smbd[552]: [ID 413393 daemon.error] dyndns: failed
to get domainname
Nov 20 23:50:46 sta-nas-01 last message repeated 2 times
Nov 20 23:51:07 sta-nas-01 smbd[552]: [ID 413393 daemon.error] dyndns: failed
to get domainname
Nov 20 23:54:58 sta-nas-01 last message repeated 7 times
Nov 21 00:12:34 sta-nas-01 in.routed[510]: [ID 464608 daemon.error] route
0.0.0.0 --> 192.168.101.100 nexthop is not directly connected
Nov 21 01:12:34 sta-nas-01 in.routed[510]: [ID 464608 daemon.error] route
0.0.0.0 --> 192.168.101.100 nexthop is not directly connected
Nov 21 02:12:34 sta-nas-01 in.routed[510]: [ID 464608 daemon.error] route
0.0.0.0 --> 192.168.101.100 nexthop is not directly connected
Nov 21 03:12:34 sta-nas-01 in.routed[510]: [ID 464608 daemon.error] route
0.0.0.0 --> 192.168.101.100 nexthop is not directly connected
Nov 21 04:17:33 sta-nas-01 in.routed[510]: [ID 464608 daemon.error] route
0.0.0.0 --> 192.168.101.100 nexthop is not directly connected
Nov 21 05:17:33 sta-nas-01 in.routed[510]: [ID 464608 daemon.error] route
0.0.0.0 --> 192.168.101.100 nexthop is not directly connected
Nov 21 06:17:33 sta-nas-01 in.routed[510]: [ID 464608 daemon.error] route
0.0.0.0 --> 192.168.101.100 nexthop is not directly connected
Nov 21 07:17:33 sta-nas-01 in.routed[510]: [ID 464608 daemon.error] route
0.0.0.0 --> 192.168.101.100 nexthop is not directly connected
Nov 21 08:17:33 sta-nas-01 in.routed[510]: [ID 464608 daemon.error] route
0.0.0.0 --> 192.168.101.100 nexthop is not directly connected
Nov 21 09:17:33 sta-nas-01 in.routed[510]: [ID 464608 daemon.error] route
0.0.0.0 --> 192.168.101.100 nexthop is not directly connected
Nov 21 10:17:33 sta-nas-01 in.routed[510]: [ID 464608 daemon.error] route
0.0.0.0 --> 192.168.101.100 nexthop is not directly connected
Nov 21 11:17:33 sta-nas-01 in.routed[510]: [ID 464608 daemon.error] route
0.0.0.0 --> 192.168.101.100 nexthop is not directly connected
Does that help? I setup a zone to run tomcat on the same box and we also have a
VirtualBox image of Windows 2003 which is used to synchronise our backups with
another server (remotely) using Acronis.
Thanks,
Em
Date: Fri, 20 Nov 2009 18:30:01 -0600
Subject: Re: [zfs-discuss] CIFS shares being lost
From: t...@cook.ms
To: emilygrettelis...@hotmail.com
CC: zfs-discuss@opensolaris.org
On Fri, Nov 20, 2009 at 6:17 PM, Emily Grettel <emilygrettelis...@hotmail.com>
wrote:
Hi,
I'm just starting out on ZFS and OpenSolaris (2009.06) and I'm having an issue
with CIFS shares not working after a while. I have about 30 users, I've updated
our NT scripts to mount the share at startup and this works OK. If I leave the
server up, after a day the CIFS stop working.
I have 4 file systems on a raidz2 zpool, all four of these are visible as CIFS
shares.
I'm not sure how to debug or look for where things may be going awry, could
anyone tell me or point me in the right direction?
Thanks,
Emily
--
Emily
CIFS information generally gets dumped into /var/adm/messages. What do you
mean by "it stops working". You have to remount the shares? You have the
reboot the server? What is the process to make it "work" again?
--
--Tim
_________________________________________________________________
Looking to move this spring? With all the lastest places, searching has never
been easier. Look now!
http://clk.atdmt.com/NMN/go/157631292/direct/01/_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
