[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: AW: dd killed with USR1 right after ftruncate()
From: |
Jim Meyering |
Subject: |
Re: AW: dd killed with USR1 right after ftruncate() |
Date: |
Thu, 13 Aug 2009 14:09:20 +0200 |
Voelker, Bernhard wrote:
> Pádraig wrote:
>
>> What is your exact dd command please, and destination file system.
>
> I was running KNOPPIX 5.3.1; the source was a harddisk partition, and
> the target was a file in an ext2 filesystem on a harddisk in an USB device
> mounted on /media/sdb2/:
>
> $ dd if=/dev/sda5 of=/media/sdb2/backups/sda5 bs=1G
>
>> I'm a bit confused as ftruncate is not called unless you specify a
>> non zero seek= but that seems a bit weird from your described usage.
>
> hmm, so maybe it has not actually been the truncate() which took
> so long but the fd_reopen() using O_TRUNC.
Sounds like a good reason to defer SIGUSR1 from post-getopt/arg-verify
until when the copy-timer starts.
- dd killed with USR1 right after ftruncate(), Voelker, Bernhard, 2009/08/12
- Re: dd killed with USR1 right after ftruncate(), Pádraig Brady, 2009/08/13
- AW: dd killed with USR1 right after ftruncate(), Voelker, Bernhard, 2009/08/13
- Re: AW: dd killed with USR1 right after ftruncate(),
Jim Meyering <=
- Re: AW: dd killed with USR1 right after ftruncate(), Pádraig Brady, 2009/08/13
- AW: AW: dd killed with USR1 right after ftruncate(), Voelker, Bernhard, 2009/08/13
- Re: AW: AW: dd killed with USR1 right after ftruncate(), Pádraig Brady, 2009/08/13
- Re: AW: AW: dd killed with USR1 right after ftruncate(), Jim Meyering, 2009/08/13
- Re: AW: dd killed with USR1 right after ftruncate(), Jim Meyering, 2009/08/13