linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Martin Wilck <mwilck@arcor.de>
To: "David F." <df7729@gmail.com>
Cc: NeilBrown <neilb@suse.de>,
	"linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>
Subject: Re: MDADM 3.3 broken?
Date: Wed, 27 Nov 2013 23:40:11 +0100	[thread overview]
Message-ID: <529674CB.5040808@arcor.de> (raw)
In-Reply-To: <CAGRSmLsHSwELK_jd=PEckDpSBVCfrt9cHBvG_cH9esMYtLu5Jg@mail.gmail.com>

On 11/26/2013 10:59 PM, David F. wrote:
> does it need to be a tar type file or would virtual hard drive .vmdk
> files be okay?

I guess it would be ok (never tried).

Martin

  reply	other threads:[~2013-11-27 22:40 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-18 18:26 MDADM 3.3 broken? David F.
2013-11-18 20:22 ` Martin Wilck
2013-11-18 23:13   ` David F.
2013-11-19  0:01     ` NeilBrown
2013-11-19 17:05       ` David F.
2013-11-19 20:38         ` Martin Wilck
2013-11-19 22:34           ` David F.
2013-11-19 22:49           ` David F.
2013-11-19 19:45       ` Martin Wilck
2013-11-19 20:08         ` David F.
2013-11-19 23:51         ` NeilBrown
2013-11-20  0:22           ` David F.
2013-11-20  0:35             ` David F.
2013-11-20  0:48               ` NeilBrown
2013-11-20  1:29                 ` David F.
2013-11-20  1:34                   ` David F.
2013-11-20  2:30                     ` NeilBrown
2013-11-20  6:41                       ` David F.
2013-11-20 23:15                         ` David F.
2013-11-21 20:50                           ` Martin Wilck
2013-11-21 21:10                             ` David F.
2013-11-21 21:30                               ` Martin Wilck
2013-11-21 22:39                                 ` David F.
2013-11-25 21:39                                   ` Martin Wilck
2013-11-21 20:46                       ` Martin Wilck
2013-11-21 21:06                         ` David F.
2013-11-21 23:05                         ` David F.
2013-11-21 23:09                           ` David F.
2013-11-22  3:06                             ` David F.
2013-11-22 18:36                               ` David F.
2013-11-23 23:36                                 ` David F.
2013-11-25 21:56                           ` Martin Wilck
2013-11-26  0:24                             ` David F.
2013-11-26 21:59                             ` David F.
2013-11-27 22:40                               ` Martin Wilck [this message]
2013-12-06  1:53                                 ` David F.
2013-12-07  2:28                                   ` David F.
2013-12-07  3:16                                     ` NeilBrown
2013-12-07  3:46                                       ` David F.
2013-12-14 21:01                                       ` David F.
2014-01-20  4:34                                         ` NeilBrown
2014-01-20 21:52                                           ` Martin Wilck
2014-01-20 23:54                                           ` David F.
2014-01-22 22:32                                             ` David F.

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=529674CB.5040808@arcor.de \
    --to=mwilck@arcor.de \
    --cc=df7729@gmail.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=neilb@suse.de \
    /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).