https://bugzilla.novell.com/show_bug.cgi?id=409504 Cyril Hrubis changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.provo.novell.com |kernel-maintainers@forge.provo.novell.com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=409504 User robin.listas@telefonica.net added comment https://bugzilla.novell.com/show_bug.cgi?id=409504#c2 --- Comment #2 from Carlos Robinson 2008-07-23 13:37:14 MDT --- The fstab has already "ro" (see #1), but yes, it is a dvd burner drive. I think I saw this before [...] Yes, I reported a similar or same problem with XFS, Bug 280900, comment 4 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=409504 User teheo@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=409504#c4 Tejun Heo changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |robin.listas@telefonica.net --- Comment #4 from Tejun Heo 2008-07-28 00:47:48 MDT --- I don't think we can come up with a good kernel-side fix for this problem soon. Jeff, do you have any idea why the ro flag didn't work? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=409504 User jeffm@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=409504#c6 --- Comment #6 from Jeff Mahoney 2008-08-04 12:11:14 MDT --- I've posted a 10.3 i386 default kernel at http://ftp.suse.com/pub/people/jeffm/suse/testpkgs/409504/10.3-i386/ Could you give it a try? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=409504 User robin.listas@telefonica.net added comment https://bugzilla.novell.com/show_bug.cgi?id=409504#c8 Carlos Robinson changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|robin.listas@telefonica.net | --- Comment #8 from Carlos Robinson 2008-08-04 18:57:34 MDT --- Ok, I found some time while watching a boring movie. It doesn't work, I'm afraid. nimrodel:~ # uname -a Linux nimrodel 2.6.22.18-_bug409504-default #1 SMP 2008-08-04 16:57:59 +0200 i686 i686 i386 GNU/Linux nimrodel:~ # /etc/init.d/boot.crypto start /dev/dvd.l Please enter passphrase for /dev/dvd.l (mycrypt_mm_dvd): key slot 0 unlocked. Please enter passphrase for /dev/dvd.l (mycrypt_mm_dvd): Command successful. /dev/dvd.l... done nimrodel:~ # **** /var/log/kernel Aug 5 02:16:09 nimrodel kernel: eth0: no IPv6 routers present Aug 5 02:16:09 nimrodel kernel: audit(1217895367.059:68): audit_pid=4402 old=0 by auid=4294967295 Aug 5 02:16:18 nimrodel kernel: NET: Registered protocol family 17 Aug 5 02:16:18 nimrodel kernel: device eth0 entered promiscuous mode Aug 5 02:16:38 nimrodel kernel: PPP generic driver version 2.4.2 Aug 5 02:19:19 nimrodel kernel: REISERFS (device dm-1): found reiserfs format "3.6" with standard journal Aug 5 02:19:19 nimrodel kernel: REISERFS (device dm-1): using ordered data mode Aug 5 02:19:19 nimrodel kernel: reiserfs: using flush barriers Aug 5 02:19:19 nimrodel kernel: REISERFS (device dm-1): journal params: device dm-1, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 Aug 5 02:19:19 nimrodel kernel: REISERFS (device dm-1): checking transaction log (dm-1) Aug 5 02:19:20 nimrodel kernel: reiserfs: disabling flush barriers on dm-1 Aug 5 02:19:20 nimrodel kernel: REISERFS (device dm-1): Using r5 hash to sort names Aug 5 02:19:29 nimrodel kernel: hdc: command error: status=0x51 { DriveReady SeekComplete Error } Aug 5 02:19:29 nimrodel kernel: hdc: command error: error=0x50 { LastFailedSense=0x05 } Aug 5 02:19:29 nimrodel kernel: ide: failed opcode was: unknown Aug 5 02:19:29 nimrodel kernel: ATAPI device hdc: Aug 5 02:19:29 nimrodel kernel: Error: Illegal request -- (Sense key=0x05) Aug 5 02:19:29 nimrodel kernel: Invalid field in command packet -- (asc=0x24, ascq=0x00) Aug 5 02:19:29 nimrodel kernel: The failed "Write 10" packet command was: Aug 5 02:19:29 nimrodel kernel: "2a 00 00 00 41 26 00 00 02 00 00 00 00 00 00 00 " Aug 5 02:19:29 nimrodel kernel: end_request: I/O error, dev hdc, sector 66712 Aug 5 02:19:29 nimrodel kernel: Buffer I/O error on device hdc, logical block 8339 Aug 5 02:19:29 nimrodel kernel: lost page write due to I/O error on hdc Some notes to clarify things a bit, just in case. The dvd contains a reiserfs image, encrypted. cer@nimrodel:~> file -s /dev/hdc /dev/hdc: LUKS encrypted file, ver 1 [aes, cbc-essiv:sha256, sha1] UUID: bcfe5715-c092-4fea-b2dc-7951cb2 The image was first generated as a HD filesystem on a file which can be normally mounted via "/etc/init.d/boot.crypto start IMAGEFILE". Data is copied there, then umounted ("boot.crypto stop IMAGEFILE"), then the IMAGEFILE is burned normally to the dvd. The journal should thus not have anything pending. It looks as if the system tries to activate the journal, sees it can't write to it, and continues happily. The doubt is what would happen on a hard disk partition mounted RO: think of somebody doing a forensic analysis, what would happens if the kernel writes to it... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.