Displaying 3 results from an estimated 3 matches for "0000012e".
Did you mean:
0000002e
2004 Jun 19
0
Oops in journal_dirty_sync_data [ext3]
...0068 es: 0068 ss: 0068
Jun 19 09:43:26 ldu506 kernel: Process java (pid: 11287,
stackpage=f5e5d000)
Jun 19 09:43:26 ldu506 kernel: Stack: 00000000 f8866d60 00000000
00000001 00000282 00000000 c277aa90 fe38012e
Jun 19 09:43:26 ldu506 kernel: 79ebab9b c01364f5 d3d89380
c277aa90 0000011b 0000012e 084291c4 c012c0de
Jun 19 09:43:26 ldu506 kernel: ffffffff 00000000 0000012e
f7b35c2c c277aa90 00000000 0000011b d4327cec
Jun 19 09:43:26 ldu506 kernel: Call Trace: [<f8866d60>]
journal_dirty_sync_data [ext3] 0x0 (0xf5e5dee4))
Jun 19 09:43:26 ldu506 kernel: [<c01364f5>] generi...
2009 Dec 08
3
botched RAID, now e2fsck or what?
Hi all,
Somehow I managed to mess with a RAID array containing an ext3 partition.
Parenthesis, if it matters: I disconnected physically a drive while
the array was online. Next thing, I lost the right order of the drives
in the array. While trying to re-create it, I overwrote the raid
superblocks. Luckily, the array was RAID5 degraded, so whenever I
re-created it, it didn't go into sync;
2002 Oct 23
3
cupsaddsmb rpcclient error
...size: 000001ac
01cc needed: 000001ac
01d0 status: WERR_OK
000000 smb_io_printer_info_2
0000 offset: 00000194
000194 smb_io_unistr servername
0004 offset: 00000168
000168 smb_io_unistr printername
0008 offset: 00000154
000154 smb_io_unistr sharename
000c offset: 0000012e
00012e smb_io_unistr portname
0010 offset: 0000012c
00012c smb_io_unistr drivername
0014 offset: 00000108
000108 smb_io_unistr comment
0018 offset: 00000106
000106 smb_io_unistr location
001c devmode: 00000000
0020 offset: 00000104
000104 smb_io_unistr sepfil...