similar to: Between single/dup and raid1/raid1

Hello, I had a raid1 btrfs (540GB) on vanilla 3.6.3, a disk failed, and removed it at power off, plugged in a new one, partitioned it (to 110GB, by error), and added it to btrfs. I tried to remove the missing device, and it said "Input/output error" after a while. Next attempts simply gave "Invalid argument". I repartitioned, rebooted the system, and made the partition grow:

Hi list, I am using kernel 3.9.0, btrfs-progs 0.20-rc1-253-g7854c8b. I have a three disk array of level single: # btrfs fi sh Label: none uuid: 2e905f8f-e525-4114-afa6-cce48f77b629 Total devices 3 FS bytes used 3.80TB devid 1 size 2.73TB used 2.25TB path /dev/sdd devid 2 size 2.73TB used 1.55TB path /dev/sdc devid 3 size 2.73TB used 0.00 path /dev/sdb

Hello, some time ago we discussed on #btrfs that the nocow attribute for files wasn''t working (around 3.3 or 3.4 kernels). That was evident by files fragmenting even with the attribute set. Chris mentioned to find a fix quickly for that, and posted some lines of change into irc. But recently someone mentioned that 3.6-rc looks like still not respecting nocow for files. Is there really

I am having some difficulty understanding the implication of lazy evaluation mixed with DUP=F in a .Fortran call. In qr.qty from base DUP is not used as an argument so defaults to T. I am calling qr.qty with a very large array and would like to set DUP=F in the .Fortran call so that qr.qty would be defined as copied below. Is there some risk that a variable used as the argument in the original

Thanks to David Scott for noticing a glitch in dup.name(). It should be: dup.name<-function(name) { if(is.character(name)) return(sum(match(objects(1:length(search())),name,nomatch=0)) > 0) cat("Usage: dup.name(name)\n\twhere name is a character string\n") } this avoids matching part of the name... Jim

Hello, I'm trying to create my own C code for use within R. While optimizing the code I've noticed that even while only using pointers to get my data to C the time needed still depends on data (vector) size. To test this, I've created an empty C function to which I've send vectors containing various sizes of elements. The time needed for each call is measured and plotted. I would

Just found out [R 0.63, standard -v -n] : > rm(list=ls()) > gc() free total Ncells 96538 200000 Vcells 214008 250000 > hist(runif(50000)) Error: heap memory (1953 Kb) exhausted [needed 390 Kb more] which is a bit astonishing given that I still have room for 214000 double's > u1 <- runif(50000) > u2 <- runif(50000) > gc()

Hello all, My scripts, which read stdout from ssh, weren't seeing EOF from the remote session.? It was being sent, but lost.? I tracked it down to the following code, in ssh.c, at ssh_session2_open: ??????? if (stdin_null_flag) { ??????????????? in = open(_PATH_DEVNULL, O_RDONLY); ??????? } else { ??????????????? in = dup(STDIN_FILENO); ??????? } ??????? out = dup(STDOUT_FILENO);

In some tests I am getting a difference in the 7th or 8th significant digit depending on whether I set DUP=T or DUP=F in the .Fortran call below. While this is not a huge error it is bigger than I would expect and may be a symptom of another problem. Any comments or suggestions? (R1.2.2 on Solaris.) Paul Gilbert _______ genD.ARMA <- function(model, data, d=0.01, eps=1e-4, r=6, warn=F){ n

I've been using ssh without it duping stdout and stderr, and had no problems.? I think this change should be made to the master source. WHAT IS THE PROBLEM WITH SSH RIGHT NOW? It duplicates FILENO_STDOUT and FILENO_STDERR, thus there are two descriptors for each of these files.? When the remote program closes its stdout or stderr, the remote sshd sends the appropriate message to the local

That''s weird. Line 296 is just a call to FormatMessage(). Folks on the mailing list - could this be a wide character issue? Buffer too small maybe? Regards, Dan Pe?a wrote: > forgot: > > it segfaults on the win2k3 server (domain controller). > > it has _not_ segfault on my winxp pro though. > > > > # -----Original Message----- > # From: Pe?a, Botp

nouveau screens are reused for the same device node. However in the scenario where we create screen 1, screen 2, and then delete screen 1, the surrounding code might also close the original device node. To protect against this, dup the fd and use the dup'd fd in the nouveau_device. Also tell the nouveau_device that it is the owner of the fd so that it will be closed on destruction. Also make

On 13/10/17 16:22, Damien Miller wrote: > At a minimum, I think we'd have to dup2 a fd to /dev/null to > STDOUT_FILENO so writes to stdout (e.g. from ill-behaved > libraries) have somewhere to go. Would that really be useful?? Output from Ill-behaved libraries, written fd 1, already go to the same place.? Don't forget, dup does not create a new file, it creates a duplicate

I have a huge matrix on which I need to do a simple (elementwise) transformation. Two of these matrices cannot fit in the memory, so I cannot do this in R. I thought of writing some C code to do this and calling it using .C with DUP=FALSE. All I need is a simple for loop that replaces elements with their new value, something like void transform(double *a, int *lengtha) { int i; for (i=0;

Hey, I am hoping that some one on this list may be able to help me. I started investigate the possibility of forking a process, the child then attach to a pty, dup std[in|out] to the pty, then exec the ssh client. For some reason, the ssh client still prompted straight to stdin and stdout rather than through the pty that I created. There seem to be a few issues with this. Can someone tell

I would us Meetme for conferance SIP-->SIP fist. my Meetme.conf: [rooms] conf => 9999 my extensions.conf: exten => 9999,1,MeetMe(9999) But : == Parsing '/etc/asterisk/meetme.conf': Found Jun 16 10:33:22 WARNING[12100]: chan_zap.c:916 zt_open: Unable to open '/dev/zap/pseudo': No such file or directory Jun 16 10:33:22 ERROR[12100]: chan_zap.c:6969 chandup: Unable

Hello List, I'm running a ping command to monitor our connection to the Internet. Around yesterday, I was getting a lot of (DUP!) text on the replies. Would anyone know what that means? -- Stand before it and there is no beginning. Follow it and there is no end. Stay with the ancient Tao, Move with the present.

Hi Everyone, I have a piece of C code that uses R_alloc, and so I set DUP=TRUE in the call using ".C". As I understand it this takes a copy of each object passed to my function. If these objects are large then this could be expensive. My question is, if I rewrote the code to use .Call, would I avoid this duplication by using the objects themselves (they are not modified in the code)

Hi, My system has been encounter this problem, and I couldn''t find solution after debugging. My scenario is stated below: class user has_many :posts has_many :comments end class post belongs_to :user has_many :comments, :as => :commentable end class comment belongs_to :post belongs_to :user end For this case, I am trying to retrieve each post''s comment

On 14/10/17 07:44, Damien Miller wrote: > On Fri, 13 Oct 2017, David Newall wrote: >> On 13/10/17 16:22, Damien Miller wrote: >> > At a minimum, I think we'd have to dup2 a fd to /dev/null to >> > STDOUT_FILENO so writes to stdout (e.g. from ill-behaved >> > libraries) have somewhere to go. >> >> Would that really be useful?? Output from