On Tue, Oct 10 2017, Curt wrote: > On Tue, Oct 10, 2017 at 5:56 PM, NeilBrown <neilb@xxxxxxxx> wrote: >> On Tue, Oct 10 2017, Curt wrote: >> >>> On Tue, Oct 10, 2017 at 4:58 PM, Curt <lightspd@xxxxxxxxx> wrote: >>> >>>>> Can you please >>>>> mkdir /tmp/dump >>>>> mdadm --dump=/dev/dump /dev...list.all.devices.in.the.array >>>>> tar czf --sparse /tmp/dump.tgz /tmp/dump >>>>> >>>> Yeah, I will get that for you once I reboot the server. >>>> >>> Quick question. Is that supposed to be mdadm --dump=/dev/dump or /tmp/dump? >> >> "/tmp/dump" - yes, I typed the wrong thing. >> >> Thanks, >> NeilBrown > > Out of curiosity, how long should it take to tar these files? I get > the system reports them as 1.9T and there not really that big, hence > the sparse switch. I've just never tarred a sparse file file before. > It's been churning away for about 2 hours, which I'm going to assume > is normal. With a sufficiently recent 'tar' and kernel (I don't know how recent they need to be) it should be nearly instantaneous. With older code it could easily take hours. The kernel needs to support SEEK_HOLE (v3.1 introduced that) and tar need to support "--hole-detection=seek", which is the default if it is supported. I don't know what version. NeilBrown > -- > To unsubscribe from this list: send the line "unsubscribe linux-raid" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html
Attachment:
signature.asc
Description: PGP signature
