search for: sdx

Currently, if we don't enable CONFIG_OCFS2_FS_POSIX_ACL, ocfs2 will not support acl. That is OK. But in the following case: 1. kernel isn't built to support acl. 2. mount -t ocfs2 -o acl /dev/sdx /mnt/ocfs2. It sucesses. And what's more, if I do "mount|grep sdx" will get /dev/sdx on /mnt/ocfs2 type ocfs2 (rw,acl,heartbeat=none) So a normal user will just think acl now is ok for the volume and he will surely be puzzled when he tries setfacl and fails with "Operation not s...

I am trying to do a power analysis to get the number of replicas per treatment. If I try to get the power it works just fine: setn=c(2,3) sdx=c(1.19,4.35) power.t.test(n = setn, delta = 13.5, sd = sdx, sig.level = 0.05,power = NULL) If I go the other way to obtain the "n" I have problems. sdx=c(1.19,4.35) pow=c(.8,.8) power.t.test(n = NULL, delta = 13.5, sd = sdx, sig.level = 0.05, power = 0.8) Is there any way to do this? Th...

hi, on centos 5.x and fedora 6 there are hdX and sdX while from fedora 7 (and probably centos 6.x) there will be only sdX. is it possible with the latest centos kernel to use the same ata_piix driver to handle all disk (ie. both pata and sata) so we've only sdX disk devices like it's the current setup on newer fedora release. we try to disabl...

Am 22.01.2014 09:27, schrieb Ronald F. Guilmette: > In message <BLU0-SMTP46982596DE9C2639CEB6B078BA40 at phx.gbl>, Ady wrote: > >> I am going to repeat what Genec requested at some point. Please post >> the result of (replace 'sdX' with the adequate device): >> >> 'fdisk -l -c=dos -u=cylinders/dev/sdX' >> and >> 'fdisk -l -u=sectors /dev/sdX' >> >> where 'sdX' is (are) the problematic device. > I have done both of the above commands now, for each of the two U...

Nicolas Kovacs wrote: > Le 28/02/2019 ? 04:12, Jobst Schmalenbach a ?crit?: > >> I want to lock in the SDA/SDB/SDC for my drives > > In short : use UUIDs or labels instead of hardcoding /dev/sdX. > > https://wiki.archlinux.org/index.php/persistent_block_device_naming Yeah - I strongly believe in labels, given the fact that *no* one can remember a UUID.... mark

On Thu, Feb 28, 2019 at 05:19:49PM +0100, Nicolas Kovacs (info at microlinux.fr) wrote: > Le 28/02/2019 ? 04:12, Jobst Schmalenbach a ?crit?: > > I want to lock in the SDA/SDB/SDC for my drives > > In short : use UUIDs or labels instead of hardcoding /dev/sdX. I **KNOW** how to use UUID's ... this is NOT the reason why I am doing this! I *NEED* the order of the disks to be SDA(1st BIOS drive) SDB(2nd BIOS drive) SDC(3rd BIOS drive) and not SDA (1st BIOS drive) SDB(3rd BIOS drive) SDC (2nd BIOS drive). Reason: it stuffs up the use of grub2* utili...

...I created a striped set by mistake, yet I wanted the mirrored. Here starts my problem, I cannot get rid of the /dev/mdX no matter what I do (try to do). I tried to delete the MDX, I removed the disks by failing them, then removing each array md0, md1 and md2. I also did dd if=/dev/zero of=/dev/sdX bs=512 seek=$(($(blockdev --getsz /dev/sdX)-1024)) count=1024 dd if=/dev/zero of=/dev/sdX bs=512 count=1024 mdadm --zero-superblock /dev/sdX Then I wiped each partition of the drives using fdisk. Now every time I start fdisk to setup a new set of partitions I see in /var/log/messages as soon...

Hello, thanks for the help. Yes And the commands to discovery iscsi results ok Such iscsiadm --mode discovery --type sendtargets And scsiadm -m node -T And the disks appear on pvdisplay 2018-03-14 16:23 GMT-03:00 Marcelo Roccasalva < marcelo-centos at irrigacion.gov.ar>: > On Wed, Mar 14, 2018 at 4:08 PM, marcos sr <msr.mailing at gmail.com> wrote: > > > >

...1:length(n)){ split <- length(data)/(n[i]) for (j in 1:(n[i]/2)){ x = data[(1 + (j-1)*(2*split)):(round(split) + (j-1)*(2*split))] dx = cbind(dx,x) y = data[((round(split)+1) + (j-1)*(2*split)):(2*j*split)] dy = cbind(dy,y) }} dx = dx[,2:dim(dx)[2]] dy = dy[,2:dim(dy)[2]] k=0 meanx=0 meany=0 sdx=0 sdy=0 nx=0 ny=0 for (k in 1:dim(dx)[2]) { meanx[k] = mean(unique(dx[,k])) meany[k] = mean(unique(dy[,k])) sdx[k] = sd(unique(dx[,k])) sdy[k] = sd(unique(dy[,k])) nx[k] = length(unique(dx[,k])) ny[k] = length(unique(dy[,k])) } t = (meanx-meany)/sqrt((sdx^2/nx) + (sdy^2/ny)) df = ((sdx^2/nx) + (s...

Hi I have read instructions for udev, I also found many example on how to do this. I want to lock in the SDA/SDB/SDC for my drives and I came up with a rule like this KERNEL=="sd?", SUBSYSTEM=="block", ENV{ID_SERIAL}=="ST500DM002-1BC142_W2A56H8A", NAME="sda", RUN+="/usr/bin/logger ID_SERIAL=$ENV{ID_SERIAL} set to /dev/sda ",

Dear R users, I am stuck trying to figure out how to make a function return one value and print another.? Here is an example function: ################## eg <- function(x, digits=4) { xbar <- mean(x) sdx <- sd(x) value <- list(xbar, sdx) names(value) <- c("Mean of X", "SD of X") return(value)} ################## My current "solution" has been to round the variables before putting them into the list.? Since it can go up to 22 digits, this is fine for my basic...

The guestfs_canonical_device_name API was rewriting /dev/mdX as /dev/sdX. This is wrong since (eg) /dev/sd0 is not a device name, so if you pass the canonicalized name back to the API it will fail. virt-v2v was one tool doing this. --- src/canonical-name.c | 1 + 1 file changed, 1 insertion(+) diff --git a/src/canonical-name.c b/src/canonical-name.c index ae7b468..d7...

...9 at 11:52 AM mark <m.roth at 5-cent.us> wrote: >> Nicolas Kovacs wrote: >>> Le 28/02/2019 ? 04:12, Jobst Schmalenbach a ?crit : >>>> I want to lock in the SDA/SDB/SDC for my drives >>> >>> In short : use UUIDs or labels instead of hardcoding /dev/sdX. >>> >>> https://wiki.archlinux.org/index.php/persistent_block_device_naming >> >> Yeah - I strongly believe in labels, given the fact that *no* one can >> remember a UUID.... > > ls -l /dev/disk/by-uuid > (copy) > (paste) That is, of course, assumin...

Le 28/02/2019 ? 04:12, Jobst Schmalenbach a ?crit?: > I want to lock in the SDA/SDB/SDC for my drives In short : use UUIDs or labels instead of hardcoding /dev/sdX. https://wiki.archlinux.org/index.php/persistent_block_device_naming Cheers, Niki -- Microlinux - Solutions informatiques durables 7, place de l'?glise - 30730 Montpezat Site : https://www.microlinux.fr Blog : https://blog.microlinux.fr Mail : info at microlinux.fr T?l. : 04 66 63 10 32

...8, 2019 at 11:52 AM mark <m.roth at 5-cent.us> wrote: > Nicolas Kovacs wrote: > > Le 28/02/2019 ? 04:12, Jobst Schmalenbach a ?crit : > > > >> I want to lock in the SDA/SDB/SDC for my drives > > > > In short : use UUIDs or labels instead of hardcoding /dev/sdX. > > > > https://wiki.archlinux.org/index.php/persistent_block_device_naming > > Yeah - I strongly believe in labels, given the fact that *no* one can > remember a UUID.... > > mark > ls -l /dev/disk/by-uuid (copy) (paste) -- *Matt Phelps* *Information T...

...e anything. MAYBE, if you're in a Google or Amazon > datacenter, with 500,000 physical servers (I phone interviewed with them > 10 years ago)... but short of that? Nope. You can (perhaps should...) use the World Wide Name, which is a manufacturer ID unique to each disk. Contrary to the /sdX, it doesn't change with different configurations, OS or computer. An example of such an ID is the following: /dev/disk/by-id/wwn-0x50025ee3b4f5ca61 Many modern disks have their WWN printed on their labels.

...h wrote: > On Thu, Feb 28, 2019 at 05:19:49PM +0100, Nicolas Kovacs (info at microlinux.fr) wrote: >> Le 28/02/2019 ? 04:12, Jobst Schmalenbach a ?crit?: >>> I want to lock in the SDA/SDB/SDC for my drives >> >> In short : use UUIDs or labels instead of hardcoding /dev/sdX. > > I **KNOW** how to use UUID's ... this is NOT the reason why I am doing this! > > > I *NEED* the order of the disks to be SDA(1st BIOS drive) SDB(2nd BIOS drive) SDC(3rd BIOS drive) and not SDA (1st BIOS drive) SDB(3rd BIOS drive) SDC (2nd BIOS drive). > > Reason: i...

...weights and wondering if I can get rid of the outer for loop as well. I made a simple examples which is essentially what I am doing. Thanks for your help! -Young #------------------------------------------------------ # wtd.var is Hmisc package # you can replace the 3 lines inside for loop as # sdx[i,] = apply(x[(i-4):i,],2,var,na.rm=T) # ------------------------------------------------------- x = matrix(rnorm(200),10,20) sdx = matrix(0,10,20) for(i in 5:nrow(x)){ wts = ( 0.5 )^(i-c(1:i)) wts = wts/sum(wts) sdx[i,] = apply(x[1:i,],2,wtd.var,wei...

I am trying to write a function that will simulate observed counts X and Y as below, I want the function to be able give many replicates, can somebody advise? thanks Oarabile #alpha,n sdx and sdy are constant, and N is a vector of length n. unstructured<-function(n,N,alpha,sdx,sdy){ Vx<-rnorm(n,mean=0,sd=sdx) Vy<-rnorm(n,mean=0,sd=sdy) thetax<-exp(alpha+Vx) thetay<-exp(alpha+Vy) X<-rpois(n,N*thetax) Y<-rpois(n,N*thetay) data.frame(X,Y) } set.seed() unstructure...

Tonight I have to boot a diskless server with iLO and dd a remote image available by ssh onto a usb key. As there is no local place to store the image, whats the most efficient cmd to push the image from the remote server using ssh into the local pipe pushing out to `dd of=/dev/sdx`? Would a remote execution of `dd if=/dev/sdx` be the best over ssh? I suppose I could use nc and do away with ssh, is that in the CentOS rescue mode? Thanks, jlc