search for: 85d2

...ot;is_not_partitioned_device". > +and is_ignored_gpt_type gpt_type = > + match gpt_type with You can write this as: and is_ignored_gpt_type = function | pattern -> result | ... > + (* Windows Logical Disk Manager metadata partition. *) > + | "5808C8AA-7E8F-42E0-85D2-E1E90434CFB3" -> Optgroups.ldm_available () > + (* Windows Logical Disk Manager data partition. *) > + | "AF9B60A0-1431-4F62-BC68-3311714A69AD" -> Optgroups.ldm_available () Why does the result depend on Optgroups.ldm_available ()? > + (* Microsoft Reserved Partit...

This patch series addresses comments after v6 series review. Mykola Ivanets (6): daemon: Changing the way that we detect if a device contains partitions. daemon: list-filesystems: Ignore partitioned MD devices. tests: list-filesystems command ignores partitioned MD devices. daemon: list-filesystems: Change the way we filter out LDM partitions. daemon: list-filesystems: Filter out

v8: - Rebased on top of master. v7: - Addresses comments after v6 series review. v6: - Addresses comments after v5 series review. - Large commit is splitted to more granular commits for better code review. v5: - Addresses comments after v4 series review (part_get_mbr_part_type doesn't break original implementation in C). - Rebased on top of master and little bit refactored for

This patch series: 1. Addresses comments from v5 series review 2. Large commit is splitted to more granular commits for better code review. Mykola Ivanets (6): daemon: Changing the way that we detect if a device contains partitions. daemon: list-filesystems: Ignore partitioned MD devices. tests: list-filesystems command ignores partitioned MD devices. daemon: list-filesystems: Change

This patch series: 1. Addresses comments from last review: part_get_mbr_part_type doesn't break original implementation in C. 2. Rebased on top of master and little bit refactored for readability. Mykola Ivanets (1): tests: md: Test guestfish list-filesystems command skips partitioned md devices. Nikolay Ivanets (2): daemon: Reimplement 'part_get_mbr_part_type' API in

...bout devices which just contain partitions, so we also + * exclude such devices. + *) +and check_device device = + not (is_partitioned_device device) + +and is_ignored_gpt_type gpt_type = + match gpt_type with + (* Windows Logical Disk Manager metadata partition. *) + | "5808C8AA-7E8F-42E0-85D2-E1E90434CFB3" -> Optgroups.ldm_available () + (* Windows Logical Disk Manager data partition. *) + | "AF9B60A0-1431-4F62-BC68-3311714A69AD" -> Optgroups.ldm_available () + (* Microsoft Reserved Partition. *) + | "E3C9E316-0B5C-4DB8-817D-F92DF00215AE" -> true +...

...these later. We also ignores Microsoft Reserved Partitions (MSR) + * and extended MBR partitions because they don't contain filesystem. + *) +and check_partition partition = + try + (* Windows Logical Disk Manager metadata partition. *) + let gpt_ldm_metadata = "5808C8AA-7E8F-42E0-85D2-E1E90434CFB3" in + (* Windows Logical Disk Manager data partition. *) + let gpt_ldm_data = "AF9B60A0-1431-4F62-BC68-3311714A69AD" in + (* Microsoft Reserved Partition. *) + let gpt_msr = "E3C9E316-0B5C-4DB8-817D-F92DF00215AE" in + + let device = Devsparts.par...

Initial discussion is here: https://www.redhat.com/archives/libguestfs/2018-January/msg00188.html. v2 was posted here: https://www.redhat.com/archives/libguestfs/2018-January/msg00246.html. v3 comparing to v2 is just a rebase with slightly changed commits comments.

Instead of parsing 'parted' output OCaml implementation relies on the following facts: 1. The function is applicable for MBR partitions only (as noted in documentation and as function name suggests). 2. An attempt to call the function for non-MBR partition fails with "part_get_mbr_part_type can only be used on MBR Partitions" error and NULL is returned. 3. MBR partition table

...09:50.939021 IP 192.168.1.1.57521 > 192.168.1.255.us-srv: UDP, length 21 03:09:51.021731 IP win2k8sql2012.odc.reconnex.net.60496 > 172.20.242.255.us-srv: UDP, length 21 03:09:51.021738 IP win2k8sql2012.odc.reconnex.net.60496 > 172.20.242.255.us-srv: UDP, length 21 03:09:51.026895 IP6 fe80::85d2:4b07:699f:346f.dhcpv6-client > ff02::1:2.dhcpv6-server: dhcp6 solicit 03:09:51.338133 IP sql2k12node-2.odc.reconnex.net.50532 > 172.20.241.255.us-srv: UDP, length 21 03:09:51.338364 IP 192.168.1.7.50532 > 192.168.1.255.us-srv: UDP, length 21 03:09:51.338370 IP 192.168.1.7.50532 > 192.16...

Hey Richard, Could you share the following informations please? 1. gluster volume info <volname> 2. getfattr output of that file from all the bricks getfattr -d -e hex -m . <brickpath/filepath> 3. glustershd & glfsheal logs Regards, Karthik On Thu, Oct 26, 2017 at 10:21 AM, Amar Tumballi <atumball at redhat.com> wrote: > On a side note, try recently released health

On a side note, try recently released health report tool, and see if it does diagnose any issues in setup. Currently you may have to run it in all the three machines. On 26-Oct-2017 6:50 AM, "Amar Tumballi" <atumball at redhat.com> wrote: > Thanks for this report. This week many of the developers are at Gluster > Summit in Prague, will be checking this and respond next

...n.c:1327:afr_log_selfheal] 0-home-replicate-0: Completed metadata selfheal on 8451e180-330e-49b4-8cc9-dd341fbf97ac. sources=0 [2] sinks=1 [2017-10-25 10:40:25.441421] I [MSGID: 108026] [afr-self-heal-common.c:1327:afr_log_selfheal] 0-home-replicate-0: Completed data selfheal on 343ceb16-7a51-4480-85d2-cc7b1b471dc8. sources=0 [2] sinks=1 [2017-10-25 10:40:25.442620] I [MSGID: 108026] [afr-self-heal-metadata.c:52:__afr_selfheal_metadata_do] 0-home-replicate-0: performing metadata selfheal on 343ceb16-7a51-4480-85d2-cc7b1b471dc8 [2017-10-25 10:40:25.445717] I [MSGID: 108026] [afr-self-heal-common...