|Subject:||xfsdump manual page inaccurate for -b option?|
|From:||Jeremy Jackson <jerj@xxxxxxxxxxxx>|
|Date:||Fri, 04 Jun 2004 16:15:27 -0400|
|User-agent:||Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040122 Debian/1.6-1|
I'm reading xfsdump/common/drive_scsitape.c:calc_best_blk_and_rec_sz() and it seems that the manual page is inaccurate regarding the -b switch.
It indicated a 1MiB default, but reading the code, it looks like if -m is not used and if -b is not used, and the device is a local (not rmt) tape device, then the block size defaults to the lesser of the drive's maximum blocksize, or STAPE_MAX_RECSZ
A description of tape records (vs tape blocks) would be helpful also.
-- Jeremy Jackson Coplanar Networks (519)897-1516 http://www.coplanar.net
|<Prev in Thread]||Current Thread||[Next in Thread>|
|Previous by Date:||Re: Scan after crash, Chris Wedgwood|
|Next by Date:||Re: XFS for postgres databases?, Jeffrey W. Baker|
|Previous by Thread:||Re: XFS for postgres databases?, Jeremy Jackson|
|Next by Thread:||Re: xfsdump manual page inaccurate for -b option?, Tim Shimmin|
|Indexes:||[Date] [Thread] [Top] [All Lists]|