Does TRU-64 support devices with block sizes > 512 bytes/block ?

Does TRU-64 support devices with block sizes > 512 bytes/block ?

Post by Peter Kapin » Fri, 22 Mar 2002 10:02:47



I have a fibre channel device that supports block sizes
greater than 512 bytes per block.  disklabel indicates
that it cannot write the label.  Are devices like this
supported in 5.1A ?
 
 
 

Does TRU-64 support devices with block sizes > 512 bytes/block ?

Post by Bob Harri » Fri, 22 Mar 2002 11:04:26




X I have a fibre channel device that supports block sizes
X greater than 512 bytes per block.  disklabel indicates
X that it cannot write the label.  Are devices like this
X supported in 5.1A ?

No

 
 
 

Does TRU-64 support devices with block sizes > 512 bytes/block ?

Post by sen » Sat, 23 Mar 2002 01:42:40





> X I have a fibre channel device that supports block sizes
> X greater than 512 bytes per block.  disklabel indicates
> X that it cannot write the label.  Are devices like this
> X supported in 5.1A ?

> No

 hello Bob Harris

  i have some similar(?) prb : it seems that  a DLT7000
  attached throught a point to point Fc connection
  does not support variable tape block size
  i use /dev/ntape/tapeX  created by /sbin/dn_setup -boot
  to synchronize dsfmgr with kernel.
  DLT7000 support variable factor blocking.

  if i do :
  mt -f /dev/ntape/tapeX  rewind
  dd if=XXX of=/dev/ntape/tapeX bs=1024 count=10
  dd if=XXX of=/dev/ntape/tapeX bs=128k count=10
  mt -f /dev/ntape/tapeX  rewind
  mt -f /dev/ntape/tapeX  fsf 1

lead to :
  /dev/ntape/tape2 fsf 1 failed: I/O error

  I'm unable to find  information about variable size
  tz man page does not contain any usefull info about
  the right device to use.

  regards.

 
 
 

Does TRU-64 support devices with block sizes > 512 bytes/block ?

Post by Bob Harri » Sat, 23 Mar 2002 06:26:07


X


X >
X > X I have a fibre channel device that supports block sizes
X > X greater than 512 bytes per block.  disklabel indicates
X > X that it cannot write the label.  Are devices like this
X > X supported in 5.1A ?
X >
X > No
X >
X
X
X
X  hello Bob Harris
X
X
X   i have some similar(?) prb : it seems that  a DLT7000
X   attached throught a point to point Fc connection
X   does not support variable tape block size
X   i use /dev/ntape/tapeX  created by /sbin/dn_setup -boot
X   to synchronize dsfmgr with kernel.
X   DLT7000 support variable factor blocking.
X
X   if i do :
X   mt -f /dev/ntape/tapeX  rewind
X   dd if=XXX of=/dev/ntape/tapeX bs=1024 count=10
X   dd if=XXX of=/dev/ntape/tapeX bs=128k count=10
X   mt -f /dev/ntape/tapeX  rewind
X   mt -f /dev/ntape/tapeX  fsf 1
X
X lead to :
X   /dev/ntape/tape2 fsf 1 failed: I/O error
X
X
X   I'm unable to find  information about variable size
X   tz man page does not contain any usefull info about
X   the right device to use.

I hope someone else can help you, because I have not really used tape
devices since the days of 9-track 2400bpi tapes.  These new fangled
cartridge tapes are just plain strange to me :-)

                                        Bob Harris

 
 
 

Does TRU-64 support devices with block sizes > 512 bytes/block ?

Post by Peter Kapin » Sat, 23 Mar 2002 06:30:41


Bob:

Thanks for the reply.  Do you know if other block sizes will ever
be supported ?

Also, why then should I specify the block size in the DDR record ?

Peter




> X I have a fibre channel device that supports block sizes
> X greater than 512 bytes per block.  disklabel indicates
> X that it cannot write the label.  Are devices like this
> X supported in 5.1A ?

> No

 
 
 

Does TRU-64 support devices with block sizes > 512 bytes/block ?

Post by Bob Harri » Sat, 23 Mar 2002 13:54:02




X Bob:
X
X Thanks for the reply.  Do you know if other block sizes will ever
X be supported ?

    Anything is possible in the future.  The tricky is predicting if
that future will actually occur, and when in the future it might occur.

    At the current time I do not know of any release currently in
development that supports anything other than 512 byte sectors.  Now
that could change at any time since managers don't tell me what they are
thinking.  And now we are back to predicting the future :-)

X Also, why then should I specify the block size in the DDR record ?

    Not knowing what a DDR record is, I can not answer that question.

                                        Bob Harris

 
 
 

1. FreeBSD File System 512 byte-blocks --> 1024 byte-blocks

I was installing FreeBSD 2.1 several times trying to get things right
and I noticed that on my last install, the df command would return file
system block sizes of 512 bytes. All of my previous installs were of
1024 byte blocks. I always used the auto feature during the
partition. Does anyone know why it changed? And is it possible to change
the block size back to 1024bytes w/o reinstalling FreeBSD? ...what
gives?

Any suggestions would be appreciated.

Hook Hua

2. Help!I just compiled kernel 2.0.1 and now I get a kernel panic!

3. cdrw 512 byte block size jumper

4. nt cannot browse network (samba)

5. Support for ISO9660 CDROMS with 512 byte logical blocks?

6. SMC EtherPower-tulip.o module help!

7. UFS block size > 512

8. AIX 4.3 Interfaces for Windows?

9. 512 byte blocks?

10. Will HP-UX or Tru-64 survive?

11. tripwire compile problems on tru-64 5.1

12. "640MB optical drive" or "Support for block size > 1K"

13. 64-bit block sizes on 32-bit systems