Displaying 20 results from an estimated 1100 matches similar to: "URGENT:WIN2K MISSING VOLUMENAME"
2000 Mar 23
1
URGENT: WIN2K INVALID VOLUMENAME
Dear Samba Users
I detected a strange behaviour between Win2k Prof. and Samba and I hope
somebody can help me
fixing it.
The Bug:
=======
Samba does not correctly return the volume name back to win2k.
In the man pages it is written that by default the sharename is returned as
volumename.
This works fine for Win98 and NT4 but not for Win2k.
If I say "label v:" (needless to say that v:
2000 Mar 24
2
Samba and DOS
Greetings,
Is there any way to get Samba to interact with MS-DOS? I am
attempting to turn a Linux box into a VPN router for DOS clients. What I
need to know is, can I get a CIFS protocol stack for MS-DOS, is a TCP/IP
stack sufficient, are there any other solutions anyone knows about?
Thank You.
Tyrell Kumlin, Help Desk
Cipher Systems Ltd. - Providing quality software solutions & services
2017 Jul 04
0
Gluster failure due to "0-management: Lock not released for <volumename>"
The nodes have all been rebooted numerous times with no difference in outcome. The nodes are all connected to the same switch and I also replaced it to see if made any difference.
There is no issues with connectivity network wise and no firewall in place between the nodes.
I can?t do a gluster volume status without it timing out the moment the other 2 nodes are connected to the switch.
2017 Jul 04
0
Gluster failure due to "0-management: Lock not released for <volumename>"
Specifically, I must stop glusterfs-server service on the other nodes in order to perform any gluster commands on any node.
From: Victor Nomura [mailto:victor at mezine.com]
Sent: July-04-17 9:41 AM
To: 'Atin Mukherjee'
Cc: 'gluster-users'
Subject: RE: [Gluster-users] Gluster failure due to "0-management: Lock not released for <volumename>"
The nodes have
2017 Jul 05
1
Gluster failure due to "0-management: Lock not released for <volumename>"
By any chance are you having any redundant peer entries in
/var/lib/glusterd/peers directory? Can you please share the content of this
folder from all the nodes?
On Tue, Jul 4, 2017 at 11:55 PM, Victor Nomura <victor at mezine.com> wrote:
> Specifically, I must stop glusterfs-server service on the other nodes in
> order to perform any gluster commands on any node.
>
>
>
>
2002 Apr 24
0
RSYNC Error in resolving hostnames since 2.5.4
Dear Listmembers
I hope somebody can help me with the following rsync problem.
I am trying to connect (at least list the modules) to an rsync 2.4.6 server
with a 2.5.4 / 2.5.5 client.
I compiled rsync 2.5.5 on an AIX 4.3.3 and on a HP UX 11.x system and I get
the same
behaviour on both systems.
Command:
rsync oradump:: (oradump is a 2.4.6 server)
Error message:
rsync: getaddrinfo: oradump
2017 Jun 29
0
Gluster failure due to "0-management: Lock not released for <volumename>"
Thanks for the reply. What would be the best course of action? The data on the volume isn?t important right now but I?m worried when our setup goes to production we don?t have the same situation and really need to recover our Gluster setup.
I?m assuming that to redo is to delete everything in the /var/lib/glusterd directory on each of the nodes and recreate the volume again. Essentially
2017 Jun 30
3
Gluster failure due to "0-management: Lock not released for <volumename>"
On Thu, 29 Jun 2017 at 22:51, Victor Nomura <victor at mezine.com> wrote:
> Thanks for the reply. What would be the best course of action? The data
> on the volume isn?t important right now but I?m worried when our setup goes
> to production we don?t have the same situation and really need to recover
> our Gluster setup.
>
>
>
> I?m assuming that to redo is to
2017 Jun 22
0
Gluster failure due to "0-management: Lock not released for <volumename>"
Could you attach glusterd.log and cmd_history.log files from all the nodes?
On Wed, Jun 21, 2017 at 11:40 PM, Victor Nomura <victor at mezine.com> wrote:
> Hi All,
>
>
>
> I?m fairly new to Gluster (3.10.3) and got it going for a couple of months
> now but suddenly after a power failure in our building it all came crashing
> down. No client is able to connect after
2017 Jun 21
2
Gluster failure due to "0-management: Lock not released for <volumename>"
Hi All,
I'm fairly new to Gluster (3.10.3) and got it going for a couple of months
now but suddenly after a power failure in our building it all came crashing
down. No client is able to connect after powering back the 3 nodes I have
setup.
Looking at the logs, it looks like there's some sort of "Lock" placed on the
volume which prevents all the clients from connecting to
2017 Jun 27
2
Gluster failure due to "0-management: Lock not released for <volumename>"
I had looked at the logs shared by Victor privately and it seems to be
there is a N/W glitch in the cluster which is causing the glusterd to lose
its connection with other peers and as a side effect to this, lot of rpc
requests are getting bailed out resulting glusterd to end up into a stale
lock and hence you see that some of the commands failed with "another
transaction is in progress or
2018 Apr 04
0
Invisible files and directories
Hi,
I'm currently facing the same behaviour.?
Today, one of my users tried to delete a folder. It failed, saying the directory wasn't empty. ls -lah showed an empty folder but on the bricks I
found some files. Renaming the directory caused it to reappear.
We're running gluster 3.12.7-1 on Debian 9 from the repositories provided by gluster.org, upgraded from 3.8 a while ago. The
2010 May 04
1
Glusterfs and Xen - mount option
Hi,
I've installed Gluster Storage Platform on two servers (mirror) and mounted
the volume on a client.
I had to mount it using "mount -t glusterfs
<MANAGEMENT_SERVER>:<VOLUMENAME-ON-WEBGUI>-tcp <MOUNTPOINT>" because I
didn't had a vol file and couldn't generate one with volgen because we don't
have shell access to the gluster server right?
How can
2013 Nov 01
1
Hi all! Glusterfs Ipv6 support
Is Gluster 3.3.2 work with ipv6? I cant find options in CLI tu turn on and
cant fint anything about it in Admin guide.
When i search in google - i'm find workaround - add to volume config ( file
var/lib/glusterd/vols/cluster/volumename.hostname.place-metadirname )
string:
option transport.address-family inet6
to section:
volume cluster-server
type protocol/server
....
end-volume
2018 Feb 23
0
Problem migration 3.7.6 to 3.13.2
Hi Daniele,
Do you mean that the df -h output is incorrect for the volume post the
upgrade?
If yes and the bricks are on separate partitions, you might be running into
[1]. Can you search for the string "option shared-brick-count" in the files
in /var/lib/glusterd/vols/<volumename> and let us know the value? The
workaround to get this working on the cluster is available in [2].
2018 Jan 02
0
Wrong volume size with df
For what it's worth here, after I added a hot tier to the pool, the brick
sizes are now reporting the correct size of all bricks combined instead of
just one brick.
Not sure if that gives you any clues for this... maybe adding another brick
to the pool would have a similar effect?
On Thu, Dec 21, 2017 at 11:44 AM, Tom Fite <tomfite at gmail.com> wrote:
> Sure!
>
> > 1 -
2018 Feb 23
1
Problem migration 3.7.6 to 3.13.2
Thanks for replay. I founded this values
datastore_temp.serda1.glusterfs-p1-b1.vol: option shared-brick-count 2
datastore_temp.serda1.glusterfs-p2-b2.vol: option shared-brick-count 2
datastore_temp.serda2.glusterfs-p1-b1.vol: option shared-brick-count 0
datastore_temp.serda2.glusterfs-p2-b2.vol: option shared-brick-count 0
I need to change the values of serda2 node?!
2018-02-23
2017 Dec 21
3
Wrong volume size with df
Sure!
> 1 - output of gluster volume heal <volname> info
Brick pod-sjc1-gluster1:/data/brick1/gv0
Status: Connected
Number of entries: 0
Brick pod-sjc1-gluster2:/data/brick1/gv0
Status: Connected
Number of entries: 0
Brick pod-sjc1-gluster1:/data/brick2/gv0
Status: Connected
Number of entries: 0
Brick pod-sjc1-gluster2:/data/brick2/gv0
Status: Connected
Number of entries: 0
Brick
2017 Dec 21
0
Wrong volume size with df
Could youplease provide following -
1 - output of gluster volume heal <volname> info
2 - /var/log/glusterfs - provide log file with mountpoint-volumename.log
3 - output of gluster volume <volname> info
4 - output of gluster volume <volname> status
5 - Also, could you try unmount the volume and mount it again and check the size?
----- Original Message -----
From:
2005 Feb 07
7
win32-driveinfo in CVS
Hi all,
I committed win32-driveinfo 0.1.0 to CVS.
What is it?
===========
A class for getting information of drives
Synopsis
========
include Win32::DriveInfo
(sectorsPerCluster,
bytesPerSector,
numberOfFreeClusters,
totalNumberOfClusters,
freeBytesAvailableToCaller,
totalNumberOfBytes,
totalNumberOfFreeBytes) = getDriveSpace(''c'').to_a