search for: dev_stat

...andran <nbalacha at redhat.com <mailto:nbalacha at redhat.com>> wrote: > Hi, > > Please provide the gluster volume info. Do you see any errors in the client mount log file (/var/log/glusterfs/var-lib-mountedgluster.log)? root at int-gluster-01:/var/log/glusterfs # grep 'dev_static' *.log|grep -v cmd_history glusterd.log:[2017-11-05 22:37:06.934787] W [glusterd-locks.c:675:glusterd_mgmt_v3_unlock] (-->/usr/lib64/glusterfs/3.12.2/xlator/mgmt/glusterd.so(+0x22e5a) [0x7f5047169e5a] -->/usr/lib64/glusterfs/3.12.2/xlator/mgmt/glusterd.so(+0x2cdc8) [0x7f5047173dc8] --&...

...lacha at redhat.com> > wrote: > >> Hi, >> >> Please provide the gluster volume info. Do you see any errors in the >> client mount log file (/var/log/glusterfs/var-lib-mountedgluster.log)? >> > > > root at int-gluster-01:/var/log/glusterfs # grep 'dev_static' *.log|grep -v > cmd_history > > glusterd.log:[2017-11-05 22:37:06.934787] W [glusterd-locks.c:675:glusterd_mgmt_v3_unlock] > (-->/usr/lib64/glusterfs/3.12.2/xlator/mgmt/glusterd.so(+0x22e5a) > [0x7f5047169e5a] -->/usr/lib64/glusterfs/3.12.2/xlator/mgmt/glusterd.so(+0x2cd...

Do the users have permission to see/interact with the directories, in addition to the files? On Mon, Nov 6, 2017 at 1:55 PM, Nithya Balachandran <nbalacha at redhat.com> wrote: > Hi, > > Please provide the gluster volume info. Do you see any errors in the > client mount log file (/var/log/glusterfs/var-lib-mountedgluster.log)? > > > Thanks, > Nithya > > On 6

...on the system on which you are running the mount process. > > Please provide the volume config details as well (gluster volume info) from one of the server nodes. > Oh I'm sorry, I totally misread that - didn't realise it was on the client. Clarification for below logs: - 'dev_static' is the gluster volume. - 'int-kube-01' is the gluster client. - '10.51.70.151' is the first node in a three node (2 replica, 1 arbiter) gluster cluster. - '/var/lib/kubelet/...../iss3dev-static' is a directory on the client that should be mounting '10.51.70.151:/d...

> Clarification for below logs: > > - 'dev_static' is the gluster volume. > - 'int-kube-01' is the gluster client. > - '10.51.70.151' is the first node in a three node (2 replica, 1 arbiter) gluster cluster. > - '/var/lib/kubelet/...../iss3dev-static' is a directory on the client that should be mounting '...

Changes v1-v2: - Remove restriction that BTRFS_IOC_GET_DEVICE_STATS is a privileged operation - Cast u64 to unsigned long long for printf() Changes v2-v3: - Rebased on Chris'' current master Changes v3-v4: - Add padding at end of ioctl structure Changes v4-v5: - The statistic members in the ioctl are now organized as an array of 64 bit values. Symbolic names for the array indexes

Hi, Is the dev_state can also be used to track a mobile phone's status via SIP? I tried it on several phones(nokia, samsung) but it returns NOANSWER but i can hear a beep beep beep sound indicating that it is currently busy. regards, RYAN ICASIANO

I've connected some analogic phone to some fxs modules on an analogic card. I want to disable by default the call waiting sound. I know that dialing *70 before to call the call waiting is disabled until the next call, but isn't there a setting or a dialplan command to set up this automatically? Thanks -- /*************/ nik600 https://sourceforge.net/projects/ccmanager

...ch for, and the HVM timer bug which Dexan has just tracked down. And now I find that I''m having some kind of problem with the emulated hard disk. The OpenSUSE installer provides me with a shell prompt on Ctrl-Alt-F2 in which dmesg shows many repetions of: ata2: DRQ=1 with device error, dev_stat 0x49 ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen ata2.00 cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x4a data 8 in res 41/50:03:00:00:20/00:00:00:00:00/a0 Emask 0x3 (HSM violation) ata2: soft resetting link ata2.00: configured for MWDMA2 ata2: EH pend...

...the original filesystem is overwritten with that of the snapshot in /proc/mounts. Steps to reproduce: arnd@kallisto:/mnt$ sudo mount /dev/vg0/original /mnt/original [ 107.041432] device fsid 5c3e8ca2-da56-4ade-9fef-103a6a8a70c2 devid 1 transid 4 /dev/mapper/vg0-original [ 107.044691] btrfs: no dev_stats entry found for device /dev/mapper/vg0-original (devid 1) (OK on first mount after mkfs) arnd@kallisto:/mnt$ cat /proc/mounts | grep /mnt /dev/mapper/vg0-original /mnt/original btrfs rw,relatime,ssd,space_cache 0 0 arnd@kallisto:/mnt$ sudo lvcreate -L 10M --snap --name snapshot /dev/vg0/origina...

...lt;stdarg.h> #include <errno.h> #include <sys/ioctl.h> #include <string.h> #include <strings.h> #include <sys/mtio.h> #include <sys/types.h> #include <sys/stat.h> #include <fcntl.h> #include <ctype.h> #define FALSE 0 #define TRUE 1 #define dev_state(dev, state) ((dev)->state & (state)) /* Device state bits */ #define ST_OPENED (1<<0) /* set when device opened */ #define ST_TAPE (1<<1) /* is a tape device */ #define ST_FILE (1<<2) /* is a file device */ #define ST_FIFO (1<<3) /*...

My kernel crashed for some other reason, and now I can''t mount my btrfs filesystem. I don''t care about the data, it''s backed up. I''ll compile a 3.5 kernel, but is there any info you''d like off that filesystem to see why btrfs is crashing on mount? Marc [ 313.152857] device label btrfs_pool1 devid 1 transid 20769 /dev/mapper/disk1 [ 313.171318]

...= mpt_get_cb_idx(MPTSTM_DRIVER); diff --git a/drivers/misc/mei/hbm.c b/drivers/misc/mei/hbm.c index a97eb5d47705..686e8b6a4c55 100644 --- a/drivers/misc/mei/hbm.c +++ b/drivers/misc/mei/hbm.c @@ -1375,11 +1375,10 @@ int mei_hbm_dispatch(struct mei_device *dev, struct mei_msg_hdr *hdr) dev->dev_state = MEI_DEV_POWER_DOWN; dev_info(dev->dev, "hbm: stop response: resetting.\n"); /* force the reset */ return -EPROTO; - break; case CLIENT_DISCONNECT_REQ_CMD: dev_dbg(dev->dev, "hbm: disconnect request: message received\n"); disconnect_req = (struct hb...

...= mpt_get_cb_idx(MPTSTM_DRIVER); diff --git a/drivers/misc/mei/hbm.c b/drivers/misc/mei/hbm.c index a97eb5d47705..686e8b6a4c55 100644 --- a/drivers/misc/mei/hbm.c +++ b/drivers/misc/mei/hbm.c @@ -1375,11 +1375,10 @@ int mei_hbm_dispatch(struct mei_device *dev, struct mei_msg_hdr *hdr) dev->dev_state = MEI_DEV_POWER_DOWN; dev_info(dev->dev, "hbm: stop response: resetting.\n"); /* force the reset */ return -EPROTO; - break; case CLIENT_DISCONNECT_REQ_CMD: dev_dbg(dev->dev, "hbm: disconnect request: message received\n"); disconnect_req = (struct hb...