Hi,
Andrew F Comly wrote:
> You said earlier that 512 is the default block size.
The default of program "dd", to be exacting.
Block size is normally a property of devices and filesystems.
Many devices offer direct random access only at the granularity of
their block size.
E.g. a C
Thomas,
You said earlier that 512 is the default block size. But I looked up that "bs"
also refers to block size.
e.g.
"dd bs=1M count=613"
Analyzing:
bs=1M; 1M = 1Mibibyte;
1Mibibyte = 1048576 bytes; 1048576 bytes / 512 bytes/block = 2048 blocks
Thus
1M = 2048 blocks of
ion is how would i mitigate that issue. by purchasing a SAS or
SSD or can i handle it by customizing the block size. how can i determine
what is needed?
Thanks,
MYK
On Vi, 21 nov 14, 12:41:35, Karl E. Jorgensen wrote:
>
> Nowadays disks may hide this in their interface, but on the physical
> media (I'm thinking of spinning rusty platters), we still have to obey
> the laws of physics. Changing the magnetisation of a single spot is on
> neigh-impossible without
I want to clear my confusion on block size.
> theoretically i know what block size is but practically i dont know that what
> are the reasons that one might want to change the block size and how it
> effects
> the IO performance.
Well.. Block sizes exist at multiple levels...
The p
Dear experts,
i know its frustrating because i always ask theoretical question. i hope
and believe you guyz will not mind and i really learn alot from this list.
So, coming to the point, I want to clear my confusion on block size.
theoretically i know what block size is but practically i dont
On 08/11/2010 09:45 AM, Bill wrote:
> Hi folks,
>
> What's a good block size to use with tar? ie -b --blocking factor
>
> In a hard disk to hard disk and DVD backup scheme, the term
> block size gets used in at least six different ways. There are
> the blocks on the
any meaningful property of the drive.
>Now since 16065 factors as 119 x
>135, I figure I could theoretically use a blocking factor with
>tar of anywhere between 1 and 135. 20 is the default but
>realistically what block size should I use?
119
--
Boyd Stephen Smith Jr.
Hi folks,
What's a good block size to use with tar? ie -b --blocking factor
In a hard disk to hard disk and DVD backup scheme, the term
block size gets used in at least six different ways. There are
the blocks on the source hard disk - in this case 512B in size
(at least until next year
On Friday 10 September 2004 07:59, Gabor Melis wrote:
> After heavy googling I tried passing tar the block size explicitly with -b
> (for both invocations). It is not until '-b 216' that tar finally manages
> to read back the archive. I can find no documentation for the Qua
This box is a Dell Poweredge 2600 running Debian/Sarge with kernel 2.6.8. The
problem is with the tape:
# tar cf /dev/st0 /lib/modules/2.6.8-1-686-smp/
# tar xfv /dev/st0
After heavy googling I tried passing tar the block size explicitly with -b
(for both invocations). It is not until '-
Gururajan Ramachandran wrote:
Hello,
If I want to clone a hard disk drive using "dd", can I
just use an arbitrarily large block size to speed up
the process?
For example,
dd if=/dev/hda bs=32768k of=/dev/hdc
or is the block size dependent on something and has to
be carefully chosen?
Hello,
If I want to clone a hard disk drive using "dd", can I
just use an arbitrarily large block size to speed up
the process?
For example,
dd if=/dev/hda bs=32768k of=/dev/hdc
or is the block size dependent on something and has to
be carefully chosen?
What block size should I
strawks writes:
Hi,
You can use dumpe2fs from the e2fsprogs pkg :
dumpe2fs -h
I think it works on 2.4.x and 2.6.x kernel.
strawks.
Great.
Kenneth.
On Thu, 2004-04-15 at 14:00, [EMAIL PROTECTED] wrote:
Hi.
How can i find which block size my ext2 or ext3 filesystem uses? Can I use
same
Hi,
You can use dumpe2fs from the e2fsprogs pkg :
dumpe2fs -h
I think it works on 2.4.x and 2.6.x kernel.
strawks.
On Thu, 2004-04-15 at 14:00, [EMAIL PROTECTED] wrote:
> Hi.
> How can i find which block size my ext2 or ext3 filesystem uses? Can I use
> same method on 2.4.x and 2.6
Hi.
How can i find which block size my ext2 or ext3 filesystem uses? Can I use
same method on 2.4.x and 2.6.x kernel?
Thanks for answer.
Kenneth.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On Fri, Dec 28, 2001 at 01:49:42PM -0800, Mark Lanett wrote:
> > FUD! Tar does handle hard links!
> > Try it, before misleading innocent people:)
>
> Well that's good. So why doesn't the --help or man page mention it?
Because deeper information is to be found in the info pages?
--
groetjes, ca
> FUD! Tar does handle hard links!
> Try it, before misleading innocent people:)
Well that's good. So why doesn't the --help or man page mention it?
~mark
On Fri, Dec 28, 2001 at 12:52:26AM -0800, Mark Lanett wrote:
> No, don't use tar for system mirroring, it doesn't handle hard links.
> /usr/share is full of them (locales). Tar is only good for user-level stuff.
FUD! Tar does handle hard links!
Try it, before misleading innocent people:)
The onl
On Friday 28 December 2001 04:52, Mark Lanett wrote:
> No, don't use tar for system mirroring, it doesn't handle hard links.
> /usr/share is full of them (locales). Tar is only good for user-level
> stuff.
I have gone thru several harddisk-wide reformats using backups made
from tar -lcjvf (I beli
No, don't use tar for system mirroring, it doesn't handle hard links.
/usr/share is full of them (locales). Tar is only good for user-level stuff.
Just use rsync for the initial and subsequent incremental backups.
~mark
> Someone mentioned I should specify a block size. What
> would be a good block size for 60G HD?
don't do that. use tar.
really, you can have a LOT of subtle problems.
so don't do that. use tar.
well, tar instead of dd. rsync is fine. you can even make the initial
copy with rsync, and avoid tar.
pietro.
I have a second HD I am using as a mirror for my first.
I am going to use dd to initially copy files from one
to the other and then rsync on a daily basis.
Do I need to format hdb before dd if=dev/hda of=/dev/hdb?
Someone mentioned I should specify a block size. What
would be a good block size
Strange, I thought the default block size for an ISO9660 filesystem was 2048.
I'm not
sure what this block size refers too. I'm not sure what exactly would happen if
you
changed it.
Pierfrancesco Caci wrote:
> I have a scsi cdrom (Plextor) and a scsi cdwriter (Yamaha). They
I have a scsi cdrom (Plextor) and a scsi cdwriter (Yamaha). They both
have a jumper to set the block size to 1024 bytes or to 512 bytes. The
manuals say that for Unix 512 is the good value.
Do you have any suggestions? What does this value mean, after all?
Pf
"Chris Hoover" <[EMAIL PROTECTED]> writes:
First, it'd help if you wrapped the lines in your posts. Those long
lines make it look like crap in a lot of newsreaders.
| Does anyone know how to find out what the proper block size is for a
| tape drive? I have an Exabyte 8200
I too have an Exabyte 8200. Mine works, so I mention what I do,
avoiding working with an actual blocksize.
I sent this almost verbatim to another person on December 31, 1998.
Over the years, Exabyte has sold about 1 million tape drives,
so there are many on the market used, including the 8200 whic
Does anyone know how to find out what the proper block size is for a tape
drive? I have an Exabyte 8200 scsi tape drive (8mm 2.5 gig), that I bought
used with no documentation. I've looked at the exabyte home page, but did not
see any mention of block size.
I've tried to backup
28 matches
Mail list logo
