A quick look at your configuration does not show any issues.
When you say "inaccessible share" and "crashing", what exactly
you mean in technical terms? Do you see any core files for smbd?
If you haven't used coreadm(1M) to setup the core file path
then you should find files like core.smbd.xxxxx where xxxxx
would be the PID of crashed smbd in the root (/) directory
You're guessing right: being a newbie I've not used coreadm yet.
Crashing is incorrect in this technical context for there is no core
file left. But you might see from my attached log, that it seems that
some modules are doing a "turn around" as if the system is starting
(at least to me it seems so).
By saying "inaccessible" I mean, that the Windows copy process says:
"Permission denied. Make sure that the disk is not full or write
protected and the file is not in use" (well, roughly translated from
German ;-)
Trying to access the share from Windows Explorer in such a situation,
I get an error saying that the connection can not be recovered, for
the local device name is already in use.
Other than with svn_111b there doesn't seem to be a "network path not
found" anymore.
BTW: Having an error on my Windows box kills the SSH connection from
my Mac to the OpenSolaris machine -weired, oooh?
(a little later)
It's driving me mad! The copy was done from Winmerge, because I
already had some partly filled directories from the last copy attempt.
Now I tried to copy one folder directly from Windows Explorer and
succeeded (which i did not with explorer before). After this tried to
copy with Winmerge again and this time it is still runnning, having
successfully copied a third of the 2900 digital camera image files
which were due...
Is it the time of day???
Or could it be the ACL entries you mentioned below? To give a few more
hints: the Mac as well as the Windows machine are connected by cable
to the NAS; today I swapped the 100 Mbit switch and brought in a Gbit
on, but the problems have been there with both switches.
One thing about your ACL setup. Seems like you have setup your
ACLs on Solaris and not from Windows and you have used owner@
and group@ entries. These entries would not have the effect
you might expect when you start copying files from CIFS clients
and CIFS server handles the ACL inheritance. If you tell me what
exactly you were trying to achieve using owner@/group@ entries
I could give you some hints. Generally, I'd suggest that you
manage your ACLs using a Windows client if you are familiar
with how Windows ACLs work.
Oh, very easy one:
1) owner/creator of file Full Contronl, as with Windows including the
priviledge to change ownership; (default) group (named family) gets
Change (read write delete); inherited by every file or subdirectory
under the starting point (share named daten)
Inheritance breaking at subdirectories named like the users: subdir
Carsten is only accessible by carsten;
While per default all users share the same group (named family), which
has permissons regarding to 1) subdir parents breaks the inheritance
and changes the allowed group to parents, for children shall not have
access here.
Unintentional deletes should be covered by snapshots.
Afshin
Carsten
Carsten Wegner wrote:
Hello there!
I am new to OpenSolaris and all it's stuff, yet I've started to
build a "NAS for Home" on this promising technology. I've decided
to start with 2009.06 and updated to svn_118. I had some problems
with inaccessible shares from time to time and hoped for better
days with svn_118, but to me it seems things got even worse.
Although it seems possible to copy one or two file to the ZFS
share, it's constantly crashing with some more files - regardless
wether I try to copy from a Windows box or a Mac.
As far as I've read the discussions this shouldn't be a problem
anymore, should it? Please gimme help for my project in which I've
already invested money and time.
Attached you'll find a log file of "*.debug", the output of cifs-
gendiag.sh and the filesystem ACLs of the directories on the share
being accessed during the copy (these are missing from the output
of cifs-gendiag.sh). I've not set any ACLs on the share itself.
Regards
Carsten
------------------------------------------------------------------------
_______________________________________________
cifs-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/cifs-discuss
_______________________________________________
cifs-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/cifs-discuss
_______________________________________________
cifs-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/cifs-discuss
