Re: Puzzling difference between debian-arm and debian-i386 re growisofs

2008-06-13 Thread Wookey
On 2008-04-19 16:20 +0100, Barry Tennison wrote:
 For info.
 
 Additions to the bug report welcomed - especially any that reproduce it.

Are you on arm or armel? I just tried your recipie on arm (etch on a
balloonboard) (using genisoimage v1.1.2-1 ) I don't see any errors
reported but I do see both long and short versions of files suggesting
something has gone wrong with the rock ridge stuff:
$ls a
nullf000  nullfile-with-long-name

dmesg just says:
ISO 9660 Extensions: RRIP_1991A
for both successful and broken versions


Wookey
-- 
Principal hats:  Balloonz - Toby Churchill - Aleph One - Debian
http://wookware.org/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: Puzzling difference between debian-arm and debian-i386 re growisofs

2008-04-20 Thread Rick Thomas


On Apr 18, 2008, at 1:14 PM, Barry Tennison wrote:



So I think it's definitely in the genisoimage -M code, and COULD BE  
an endian issue there.




For what it proves, if anything, I tried to recreate the bug


cd somewhere safe
mkdir tmp1
touch tmp1/nullfile-with-long-name
genisoimage -R tmp1/ RR-arm-1.iso
# note: this succeeds, and then RR-arm-1.iso will loop-mount perfectly
#  well with Rock Ridge active, so nullfile-with-long-name shows with
#  the right name
genisoimage -M RR-arm-1.iso -C 0,0 -R tmp1/ RR-arm-2.iso



on a PowerMac G3 running Etch, and had no errors at all.  So simple  
endian-ness bugs seem less likely.  Complex bugs (endian or  
otherwise) are still possible, of course.


Enjoy!

Rick


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: Puzzling difference between debian-arm and debian-i386 re growisofs

2008-04-19 Thread Barry Tennison

For info.

Additions to the bug report welcomed - especially any that reproduce it.

Barry

 Original Message 
Subject: Bug#476846: Acknowledgement (genisoimage: On arm only, does not 
 recognise its own Rock Ridge extensions)

Date: Sat, 19 Apr 2008 15:06:04 +
From: [EMAIL PROTECTED] (Debian Bug Tracking System)
Reply-To: [EMAIL PROTECTED]
To: Barry Tennison [EMAIL PROTECTED]
References: [EMAIL PROTECTED]


Thank you for filing a new Bug report with Debian.

This is an automatically generated reply to let you know your message
has been received.

Your message is being forwarded to the package maintainers and other
interested parties for their attention; they will reply in due course.

Your message has been sent to the package maintainer(s):
 Joerg Jaspert [EMAIL PROTECTED]

If you wish to submit further information on this problem, please
send it to [EMAIL PROTECTED], as before.

Please do not send mail to [EMAIL PROTECTED] unless you wish
to report a problem with the Bug-tracking system.


--
476846: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=476846
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Puzzling difference between debian-arm and debian-i386 re growisofs

2008-04-15 Thread Barry Tennison
I wonder whether anyone can help a very puzzled moderately skilled 
debian and NSLU2 hacker?  Apologies for the length of explanation needed.


I have several i386 machines running etch, lenny and sid, and an NSLU2 
running etch which for some time has acted as my main fileserver.  On 
one of the i386 machines, I have a great process for backing up key data 
files to DVD, based on http://patrick.newedorf.net/backup (now only 
available from WayBackMachine - but many thanks, Patrick!) which 
produces daily, dated backups on one DVD without unnecessarily 
duplicating data.  This uses the dvd+rw-tools package, specifically 
using the growisofs command to write more data to a DVD which already 
holds some.


I am now trying to move this backup process to run directly off the NSLU2.

To summarise in the briefest possible detail, the following process 
gives different results on the NSLU2/etch and on an i386/etch:

* using a usb DVD-writer (the same one)
* burn a fresh DVD-RW (or DVD-R) with base data, using growisofs -R to 
get Rock Ridge extensions for filenames

* use growisofs to write more data to the DVD-RW (or DVD-R)

On the i386/etch, this works fine, with messages including
  Rock Ridge signatures found
On the NSLU2/etch (with the SAME usb DVD-writer and exactly the same 
scripts) the last step fails, giving messages including:

  genisoimage: **BAD RRVERSION (0) for �
  NO Rock Ridge present
  Disabling Rock Ridge / XA / AA

HOWEVER, mounting the very same DVD on the NSLU2/etch is perfectly 
successful, the Rock Ridge signatures are recognised and used.
See the PS at the end for the effectively identical mkisofs=genisoimage 
commands logged.


I am extremely puzzled by this.  Google has been no help, nor has 
searching this list; I have performed lots of experiments to elucidate 
or work around, like using -T or -udf (without success), and I can't 
follow the genisoimage/growisofs source well enough to understand what's 
going on.  I haven't tried upgrading the NSLU2 to lenny - I'd rather 
not, and the above suggests the anomaly would persist.


BTW, this does NOT seem to be the same problem as bug#457308 and its 
ilk, which seem to relate fundamentally to Mac/i386 differences.


I'm aware this may well be a dvd+rw-tools problem, but I'm avoiding 
cross-posting at this point, as it seems to involve an arm vs i386 
difference.


Anyone had a similar experience?  I'm stumped to believe any of the 
unlikely looking explanations I can think of, such as:
* the NSLU2/arm accesses the usb drive differently or sees the iso9660 
filesystem differently (but why then can it see the Rock Ridge via 
mount, but not with growisofs?  The answer may lie in the low level 
drive access used by growisofs, but would this miss the Rock Ridge??)
* the problem would go away with later versions of DVD+RW-tools (but it 
isn't there with THESE versions on i386, and the changelogs don't 
suggest any relevant fixes).


I'd be happy to provide more details, or do more experiments.  For now, 
the kernels are:

   2.6.18-6-k7 and 2.6.18-6-ixp4xx
and in both the i386 and NSLU2 contexts the software versions are:
||/ Name Version
+++--
ii  dvd+rw-tools 7.0-4
ii  genisoimage  1.1.2-1
ii  libc62.3.6.ds1-13etch5


Many thanks for reading this far!  And even more thanks for any helpful 
comments.


Barry

PS for completeness, the two growisofs outputs before the different Rock 
Ridge messages shown above are nearly identical, apart from explicable 
date/time changes:

-- on i386/etch:
Executing 'mkisofs -C 16,736 -M /dev/fd/3 -root backup-2008-04-15-18:11 
-old-root backup-2008-04-15-18:09 -quiet -R -D -graft-points /etc=/etc | 
builtin_dd of=/dev/sr0 obs=32k seek=46'

Rock Ridge signatures found
-- on NSLU2/etch:
Executing 'mkisofs -C 16,736 -M /dev/fd/3 -root backup-2008-04-15-19:14 
-old-root backup-2008-04-15-18:12 -quiet -R -D -graft-points /etc=/etc | 
builtin_dd of=/dev/sr1 obs=32k seek=46'

genisoimage: **BAD RRVERSION (0) for �
--


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: Puzzling difference between debian-arm and debian-i386 re growisofs

2008-04-15 Thread Bill Gatliff

Barry Tennison wrote:
I wonder whether anyone can help a very puzzled moderately skilled 
debian and NSLU2 hacker?  Apologies for the length of explanation needed.


Are you running out of memory on the NSLU2?


b.g.

--
Bill Gatliff
[EMAIL PROTECTED]



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]