#41 mkudffs does not read and compare

open
nobody
None
1
2004-08-16
2004-08-12
Pat LaVarre
No

mkudffs does not complain when writes fails, leaving
the blocks addressed unchange.

A reasonably reliable fix for this would be to read
those blocks back, and compare.

A less expensive fix that should work for this would be
to check the write and close return codes.

Low priority because as yet no developer has expressed
interest. High priority because more that one person
posting to linux_udf has tripped over this.

Discussion

  • Pat LaVarre

    Pat LaVarre - 2004-08-16
    • priority: 5 --> 1
     
  • Pat LaVarre

    Pat LaVarre - 2004-08-16

    Logged In: YES
    user_id=964855

    Not reproducible in 2.4.27, as quoted below.

    I have accordingly downgraded the priority of this issue to
    1 from 5.

    Maybe this rumour is entirely false? Granted, "trying to
    change type of multiple extents" means "failed for
    undistinguished causes" without quite saying so, but the
    fact remains, mkudffs does complain if asked to write at
    least some kinds of read-only discs.

    $ uname -msr
    Linux 2.4.27 i686
    $ mkudffs 2>&1 | head -1
    mkudffs 1.0.0b3 for UDF FS 1.0.0-cvs, 2004/03/09
    $ sudo rrd scan /dev/hdc /dev/scd1
    /dev/hdc is Iomega RRD 74.B rw
    /dev/scd1 is Iomega RRD 74.B rw
    $
    $ sudo dd of=/dev/hdc bs=64K seek=0 count=17 </dev/zero
    dd: opening `/dev/hdc': Read-only file system
    $ sudo dd of=/dev/scd1 bs=64K seek=0 count=17 </dev/zero
    dd: opening `/dev/scd1': Read-only file system
    $
    $ sudo mkudffs --udfrev=0x0102 /dev/hdc
    trying to change type of multiple extents
    $ sudo mkudffs --udfrev=0x0102 /dev/scd1
    trying to change type of multiple extents
    $

     

Log in to post a comment.