public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
* Re: kernel: journal /ext3 problem. "Assertion failure"
@ 2002-06-27  2:11 Philip Wyett
  2002-06-27  3:04 ` louie miranda
  0 siblings, 1 reply; 3+ messages in thread
From: Philip Wyett @ 2002-06-27  2:11 UTC (permalink / raw)
  To: linux-kernel

On Thursday 27 Jun 2002 2:58 am, louie miranda wrote:
> Jun 26 05:16:56 chsvr kernel: Assertion failure in
> journal_commit_transaction() at commit.c:535: "buffer_jdirty(bh)"
> Jun 26 05:16:56 chsvr kernel: ------------[ cut here ]------------
> Jun 26 05:16:56 chsvr kernel: kernel BUG at commit.c:535!
> Jun 26 05:16:56 chsvr kernel: invalid operand: 0000
> Jun 26 05:16:56 chsvr kernel: iptable_filter ip_tables eepro100 usb-ohci
> usbcore ext3 jbd aic7xxx sd_mod scs
> Jun 26 05:16:56 chsvr kernel: CPU:    1
> Jun 26 05:16:56 chsvr kernel: EIP:    0010:[<f88540e4>]    Not tainted
> Jun 26 05:16:56 chsvr kernel: EFLAGS: 00010286
> Jun 26 05:16:56 chsvr kernel:
> Jun 26 05:16:56 chsvr kernel: EIP is at journal_commit_transaction [jbd]
> 0xb04 (2.4.18-3smp)
> Jun 26 05:16:56 chsvr kernel: eax: 0000001c   ebx: 0000000a   ecx: c02eee60
> edx: 00003684
> Jun 26 05:16:56 chsvr kernel: esi: f7376b80   edi: f7271f00   ebp: f75aa000
> esp: f75abe78
> Jun 26 05:16:56 chsvr kernel: ds: 0018   es: 0018   ss: 0018
> Jun 26 05:16:56 chsvr kernel: Process kjournald (pid: 191,
> stackpage=f75ab000)
> Jun 26 05:16:56 chsvr kernel: Stack: f885aeee 00000217 f74d2eb8 00000000
> 00000fbc f1745044 00000000 f23a2460
> Jun 26 05:16:56 chsvr kernel:        f6558610 00001a64 00000001 f882ad2f
> f74d2e00 00000008 f1905260 edec9560
> Jun 26 05:16:56 chsvr kernel:        edec95c0 edec9620 edec9680 edec96e0
> edcbc9e0 edcbca40 edcbcaa0 edcbcb00
> Jun 26 05:16:56 chsvr kernel: Call Trace: [<f885aeee>] .rodata.str1.1 [jbd]
> 0x26e
> Jun 26 05:16:56 chsvr kernel: [<f882ad2f>] rw_intr [sd_mod] 0x20f
> Jun 26 05:16:56 chsvr kernel: [<c0119048>] schedule [kernel] 0x348
> Jun 26 05:16:56 chsvr kernel: [<f88567d6>] kjournald [jbd] 0x136
> Jun 26 05:16:56 chsvr kernel: [<f8856680>] commit_timeout [jbd] 0x0
> Jun 26 05:16:56 chsvr kernel: [<c0107286>] kernel_thread [kernel] 0x26
> Jun 26 05:16:56 chsvr kernel: [<f88566a0>] kjournald [jbd] 0x0
> Jun 26 05:16:56 chsvr kernel:
> Jun 26 05:16:56 chsvr kernel:
> Jun 26 05:16:56 chsvr kernel: Code: 0f 0b 5a 59 6a 04 8b 44 24 18 50 56 e8
> 4b f1 ff ff 8d 47 48
>
>
>
>
>
> Hi, i've encountered this error yesterday.
> The machine dont run anything big and its
> not yet on production.
>
> The machine hangs, and does not accept some
> connections on some apps like ssh, etc.
>
> I tried to reboot the machine, and after it works
> fine again.
>
> Im not sure where to send it, and not sure
> if its redhat problem or the main kernel.
>
>
>
> BTW: its redhat 7.3
> Kernel 2.4.18-3smp
> A default install so far.
>
>
> Please advise,
> louie...

This is a known ext3 issue with 7.3 SMP and kicked me in the teeth when I
installed 7.3 :). See the below link for info about the kernel update.

http://rhn.redhat.com/errata/RHBA-2002-085.html

To note this has since been superceded by a newer kernel 2.4.18-5 as against
the -4 referred too in the link. Register your system and run 'up2date' to
aquire the latest kernel and all should be well.

Regards

Philip Wyett


^ permalink raw reply	[flat|nested] 3+ messages in thread
* Re: New Zaurus Wishlist - removable media handling
@ 2002-06-27  1:40 Tomasz Rola
  2002-06-27  1:58 ` kernel: journal /ext3 problem. "Assertion failure" louie miranda
  0 siblings, 1 reply; 3+ messages in thread
From: Tomasz Rola @ 2002-06-27  1:40 UTC (permalink / raw)
  To: David Golden; +Cc: linux-kernel, zaurus-general

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Thu, 27 Jun 2002, David Golden wrote:

> 
> > And Unix filesystems were NOT designed for removable media.
> >
> 
> (LKML cc'd because this rant *might* be coherent enough to explain it
> to Linux kernel hackers)
> 
> The main problem I have with the Linux filesystems is this:
> 
> Forcing the user to think about which drive he stuck a disk or other
> removable medium into each time he wants to access it is silly - people
> often think of the disk as an entity independent of whichever drive it 
> happens to be in at the time.
> 
> It drives me crazy^Hier when software insists on its cdrom being /mnt/cdrom,
> for example  - there should be some way for the software to ask for
> "Give me a disk called xyzzy1, and I don't care what drive it is!", and 
> preferably by just trying to open e.g. /mnt/xyzzy1/
> 
> Once you've worked with a system that simply doesn't give a damn 
> what drive you put a removable disk into, or even lets you pretend an 
> arbitrary directory in the filesystem is that disk, it's very difficult to be 
> comfortable on ones that do give a damn.  
> 
> Accessing the removable medium by the volume name of the medium, _not_
>   (or not solely) by the drive it is in is something that the AmigaOS (the 
> "classic" AmigaOS, not the Intent platform plastered with Amiga-trademarks) 
> got "right", and Linux and Windows tend to get "wrong". (note the inverted 
> commas - "right" and "wrong" are merely my opinion as a one-time Amiga 
> user and now as a desktop linux user)
> 
> Amigas handled this with Assigns / amiga-style logical volumes (distinct from 
> unix/linux LVMs, which are block-level) - if you stuck a CD named xyzzy1 in 
> drive CD0:, you could access it via "CD0:" - "the volume currently in drive 
> CD0:, whatever it may be called" , or via "xyzzy1:" - " the volume called 
> xyzzy1, whatever drive it may be in"

As a former Amiga user and now yet another Linux user, I probably know
what you mean. Well, I'm not a kernel engineer but maybe it could be done
with a virtual fs like /dev - so that

1. /dev/ is not polluted
2. /mnt and other real disk space is not polluted

Having something under, say, /namespace (or, maybe /proc/namespace) could
be better than having CD0: or VirtualWhatever: and would allow to
integrate the concept into the unix way of thinking while retaining the
functionality you mean.

Of course this would also mean a new API related to the namespaces, and
they could be interfaces not only to cdroms but to IPC, for example. And,
the developers would have to be convinced to use the API :-). But speaking
only for myself, I think this is nice idea.

bye
T.

- --
** A C programmer asked whether computer had Buddha's nature.      **
** As the answer, master did "rm -rif" on the programmer's home    **
** directory. And then the C programmer became enlightened...      **
**                                                                 **
** Tomasz Rola          mailto:tomasz_rola@bigfoot.com             **

-----BEGIN PGP SIGNATURE-----
Version: PGPfreeware 5.0i for non-commercial use
Charset: noconv

iQA/AwUBPRptHBETUsyL9vbiEQLWywCdENRRHIeCpNO6UnT1BAOBsTkFLkMAoIGu
aPrmfsYUaaq8yRj1FEQdrRUo
=wQik
-----END PGP SIGNATURE-----


^ permalink raw reply	[flat|nested] 3+ messages in thread
end of thread, other threads:[~2002-06-27  3:02 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2002-06-27  2:11 kernel: journal /ext3 problem. "Assertion failure" Philip Wyett
2002-06-27  3:04 ` louie miranda
  -- strict thread matches above, loose matches on Subject: below --
2002-06-27  1:40 New Zaurus Wishlist - removable media handling Tomasz Rola
2002-06-27  1:58 ` kernel: journal /ext3 problem. "Assertion failure" louie miranda

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox