linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Marcos Dutra <macdutra@gmail.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Volume group inconsistent
Date: Mon, 23 Feb 2015 15:00:34 -0300	[thread overview]
Message-ID: <CAPcfVV_-rKdcPRKGWkMcpfd6-A=6tqbubUPqy3MHh8CKxLN=xg@mail.gmail.com> (raw)
In-Reply-To: <CAKPhfZOyg0BPTqj8fFCJbQU0iT-AstaSCpXMtwsfOCRaEd_=qQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2127 bytes --]

Thank you Eric,

Your help are welcome. I'm not an expert on LVM, but if I know something to
solve the problem, I will help them. I participated on Debian-users list,
squid, qmail and ldap, now I'm migrating my technical knowledge to LVM,
openstack and distributed file system like ceph, it's a new world for me.

I'm studying my case yet, all disks are over SAN IBM storage, so hdparm in
my case will not work at all. Unfortunately I don't have any support on OS
system (Centos), if I find something new I will post here.

Thank you

Marcos Dutra



2015-02-13 18:37 GMT-02:00 service hofman <service.hofman@googlemail.com>:

> Say something about yourself
> would you like to do something,
>  more for others.
> are you able to help you,
>
> the problem is not knowing.
>
> but the time spent.
> as to what should be excellent .
>
> what you are doing nothing,
> what you can do for others.
> LVM is a good start.
> but much remains to be done.
> look on the transport speed ,
> your hdd . what you are doing is pointless.
>
> why ?
> a transport speed of the system.
> my to 6Gb/s copy file
> hdd has 4Gb/s copy file
>
>
> ? check speed system and hdd.
> and tell me that I could change
>
> Now, ...
>  Before you change anything,
> See how it works. Do not test .
> You have always help Adding sutfix --help
> or use the performance
> prefix man
>
> And always cheak
> /usr/share/doc/ and read all the book
> Install every doc book
>
>
> Ok.
> By test recovery Hdd is Not LVM
> try not give to mount for system LVM,
> Because you lost again ....
>
> First
> Look
> Install hdparm
> hdparm -h --help.
>
> Ask for speed.
>
> Hdparm -Tt
> Hdparm -iI
>
> fdisk /dev/sdX
>
> pvs -o pv_all,gv_all,lv_all,seg_all
>
>
>
> --
> ComputerAlarmTechnologySystem©
>
> http://plus.google.com/105013137826111836446
> +44 77 04 24 74 00
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@redhat.com
> https://www.redhat.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
>

[-- Attachment #2: Type: text/html, Size: 3143 bytes --]

      reply	other threads:[~2015-02-23 18:00 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-07 15:47 [linux-lvm] Volume group inconsistent Marcos Dutra
2015-02-09  9:34 ` Zdenek Kabelac
2015-02-09 16:37   ` Marcos Dutra
2015-02-11 11:17     ` service hofman
2015-02-11 11:19       ` service hofman
2015-02-11 21:45         ` Marcos Dutra
2015-02-11 14:27     ` Zdenek Kabelac
2015-02-11 18:35       ` Marcos Dutra
2015-02-11 23:49       ` service hofman
2015-02-12 13:57         ` Marcos Dutra
2015-02-13 20:37           ` service hofman
2015-02-23 18:00             ` Marcos Dutra [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAPcfVV_-rKdcPRKGWkMcpfd6-A=6tqbubUPqy3MHh8CKxLN=xg@mail.gmail.com' \
    --to=macdutra@gmail.com \
    --cc=linux-lvm@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).