Displaying 20 results from an estimated 200 matches similar to: "Problems with Windows on KVM machine"
2017 Dec 29
2
"file changed as we read it" message during tar file creation on GlusterFS
Hi Mauro,
What version of Gluster are you running and what is your volume
configuration?
IIRC, this was seen because of mismatches in the ctime returned to the
client. I don't think there were issues with the files but I will leave it
to Ravi and Raghavendra to comment.
Regards,
Nithya
On 29 December 2017 at 04:10, Mauro Tridici <mauro.tridici at cmcc.it> wrote:
>
> Hi All,
2018 Jan 02
2
"file changed as we read it" message during tar file creation on GlusterFS
Hi All,
any news about this issue?
Can I ignore this kind of error message or I have to do something to correct it?
Thank you in advance and sorry for my insistence.
Regards,
Mauro
> Il giorno 29 dic 2017, alle ore 11:45, Mauro Tridici <mauro.tridici at cmcc.it> ha scritto:
>
>
> Hi Nithya,
>
> thank you very much for your support and sorry for the late.
> Below
2017 Dec 29
0
"file changed as we read it" message during tar file creation on GlusterFS
Hi Nithya,
thank you very much for your support and sorry for the late.
Below you can find the output of ?gluster volume info tier2? command and the gluster software stack version:
gluster volume info
Volume Name: tier2
Type: Distributed-Disperse
Volume ID: a28d88c5-3295-4e35-98d4-210b3af9358c
Status: Started
Snapshot Count: 0
Number of Bricks: 6 x (4 + 2) = 36
Transport-type: tcp
Bricks:
2018 Jan 02
0
"file changed as we read it" message during tar file creation on GlusterFS
I think it is safe to ignore it. The problem exists? due to the minor
difference in file time stamps in the backend bricks of the same sub
volume (for a given file) and during the course of tar, the timestamp
can be served from different bricks causing it to complain . The ctime
xlator[1] feature once ready should fix this issue by storing time
stamps as xattrs on the bricks. i.e. all bricks
2018 Jan 02
1
"file changed as we read it" message during tar file creation on GlusterFS
Hi Ravi,
thank you very much for your support and explanation.
If I understand, the ctime xlator feature is not present in the current gluster package but it will be in the future release, right?
Thank you again,
Mauro
> Il giorno 02 gen 2018, alle ore 12:53, Ravishankar N <ravishankar at redhat.com> ha scritto:
>
> I think it is safe to ignore it. The problem exists due to the
2010 Dec 08
4
evaluating NAs in a dataframe
Hi all,
How can one evaluate NAs in a numeric dataframe column? For example, I have
a dataframe (demo) with a column of numbers and several NAs. If I write
demo.df >= 10, numerals will return TRUE or FALSE, but if the value is
"NA", "NA" is returned. But if I write demo.df == "NA", it returns as "NA"
also. I know that I can remove NAs, but would like
1998 Mar 23
4
Browsing across subnets
I would like to know how to view a samba server on a different subnet than
the client workstation resides. For example, I have a Samba 1.9.18p3 server
in subnet 'a' and a NT 4.0 client in subnet 'b'. The Samba server does not
show up when the NT client double-clicks on the Network Neighborhood.
However, if the client does a Find:computer it will find the server, and
shares can be
2017 Sep 25
2
df command shows transport endpoint mount error on gluster client v.3.10.5 + core dump
Dear Gluster Users,
I implemented a distributed disperse 6x(4+2) gluster (v.3.10.5) volume with the following options:
[root at s01 tier2]# gluster volume info
Volume Name: tier2
Type: Distributed-Disperse
Volume ID: a28d88c5-3295-4e35-98d4-210b3af9358c
Status: Started
Snapshot Count: 0
Number of Bricks: 6 x (4 + 2) = 36
Transport-type: tcp
Bricks:
Brick1: s01-stg:/gluster/mnt1/brick
Brick2:
2010 May 07
1
Weird issue with gluster mount
Hey guys,
I have a weird issue with my glusterfs mount point.
I'm trying to touch it on one machine:
root at il-bi-s01:/mnt# touch gfs
touch: setting times of `gfs': Invalid argument
But on another machine, it works:
root at diablo /mnt # touch gfs
root at diablo /mnt #
On both machines the mount is working fine, I'm just wondering what's up with this?
CountZ
2017 Sep 26
2
df command shows transport endpoint mount error on gluster client v.3.10.5 + core dump
Hi Ashish,
thank you for your answer.
Do you need complete client log file only or something else in particular?
Unfortunately, I never used ?bt? command. Could you please provide me an usage example string?
I will provide all logs you need.
Thank you again,
Mauro
> Il giorno 26 set 2017, alle ore 09:30, Ashish Pandey <aspandey at redhat.com> ha scritto:
>
> Hi Mauro,
>
>
2017 Sep 26
2
df command shows transport endpoint mount error on gluster client v.3.10.5 + core dump
Hi Ashish,
in attachment you can find the gdb output (with bt and thread outputs) and the complete log file until the crash happened.
Thank you for your support.
Mauro Tridici
> Il giorno 26 set 2017, alle ore 10:11, Ashish Pandey <aspandey at redhat.com> ha scritto:
>
> Hi,
>
> Following are the command to get the debug info for gluster -
> gdb
2017 Sep 26
0
df command shows transport endpoint mount error on gluster client v.3.10.5 + core dump
Hi Mauro,
We would require complete log file to debug this issue.
Also, could you please provide some more information of the core after attaching to gdb and using command "bt".
---
Ashish
----- Original Message -----
From: "Mauro Tridici" <mauro.tridici at cmcc.it>
To: "Gluster Users" <gluster-users at gluster.org>
Sent: Monday, September 25,
2017 Sep 26
0
df command shows transport endpoint mount error on gluster client v.3.10.5 + core dump
Hi,
Following are the command to get the debug info for gluster -
gdb /usr/local/sbin/glusterfs <core file path>
Then on gdb prompt you need to type bt or backtrace
(gdb) bt
You can also provide the output of "thread apply all bt".
(gdb) thread apply all bt
Above commands should be executed on client node on which you have mounted the gluster volume and it crashed.
2017 Sep 27
0
df command shows transport endpoint mount error on gluster client v.3.10.5 + core dump
Hi Ashish,
I?m sorry to disturb you again, but I would like to know if you received the log files correctly.
Thank you,
Mauro Tridici
> Il giorno 26 set 2017, alle ore 10:19, Mauro Tridici <mauro.tridici at cmcc.it> ha scritto:
>
>
> Hi Ashish,
>
> in attachment you can find the gdb output (with bt and thread outputs) and the complete log file until the crash happened.
2005 Apr 12
1
functions(t.test) on variables by groups
Dear R users,
I have a data frame with categorical Vars. "Groups"
and a couple columns of numeric Vars. I am trying to
make two-sample t.test on each variable(s01-s03) by
Groups.
A data generated as following:
zot <- data.frame(Groups=rep(letters[1:2], each=4),
s01=rnorm(8), s02=rnorm(8), s03=rnorm(8))
I have written a piece with a for loop.
for (i in 1:(length(zot)-1)) {
2023 Jan 05
1
Looking for a RAID1 box
I have found a:
HPE 873830-S01 ProLiant MicroServer Gen10
for <$300 without drives.? If I can believe the seller, it has a AMD
Opteron X3216 Dual-core (2 Core) 1.6GHz and 8GB Installed.
It has 4 3.5" bays. and 1? "Media" bay?
https://www.servertechsupply.com/873830-s01/
this could well be acceptable.? Got to find out power draw.? Looks like
~40W.
Any input on issues of OS
2006 Feb 22
5
Rsync help needed...
Hello,
I was reading your posts about RSYNC. We have a massive Oracle schema lots
of datafiles about 750 GB size. We do rsync datafiles from source to target
server but everytime we cleanup the datafiles on the target server and do
rsync every 2 weeks. On the target side mostly the datafiles will be same
but on source we might have added few datafiles or made some changes in data
and as such the
2010 Apr 16
3
Delay the HungUp
Hi,
I'm tying to delay the HungUp.
I tried this way:
exten => h,1,NoOp(Start)
exten => h,n,Wait(5)
exten => h,n,NoOp(End)
exten => h,n,Hangup()
but it doesn't work, Any idea?
Thanks in advance.
2010 Sep 03
4
openvz
Can i run asterisk on a openvz vps or do i need a kernel?
I dont use dadi
2009 May 22
2
Error in FUN with tapply and by
A subset of my raw data looks like this:
--------------
"Grip" "Technique" "Baseline.integrated" "Task"
"Stroke..direction." "Engag" "Disen"
"PenDG" "PenUG" "PenDS"
"PenUS" "Duration"
-------------