Re: Read-only XFS support for FreeBSD 6-CURRENT

From: Alexander Kabaev (kan_at_FreeBSD.ORG)
Date: 03/22/05

  • Next message: vladimir_at_math.uic.edu: "USB mouse problems (5.4 BETA); vmware port" 
    Date: Tue, 22 Mar 2005 16:33:37 +0000
To: Markus Trippelsdorf <markus@trippelsdorf.de>

    On Tue, Mar 22, 2005 at 03:00:20PM +0100, Markus Trippelsdorf wrote:
    > On Tue, 2005-03-22 at 13:02 +0000, Alexander Kabaev wrote:
    > > On Tue, Mar 22, 2005 at 07:11:27AM +0100, Markus Trippelsdorf wrote:
    > > > On Mon, 2005-03-21 at 20:55 +0000, Alexander Kabaev wrote:
    > > > > The read-only XFS access was quite stable in my testing and managed to
    > > > > survive through multiple 'make -j12 buildworld' rounds with src/ stored
    > > > > on XFS partition, so I think it is a good time for a wider community to
    > > > > take it for a spin and start reporting bugs/panics that I overlooked.
    > > >
    > > > Unfortunately it does not build on my machine (AMD64):
    > > >
    > > <useless incomplete log skipped>
    > >
    > > Unfortunately you did not provide any information that can tell me
    > > what is going on on your machine. How are building XFS, as a kernel
    > > option or as a module, what is in your config file?
    >
    > The log is not that useless; because there is no -DKLD_MODULE flag, it
    > tells you that I'm trying to link XFS directly into the kernel...
    > Config is attached.
    >
    Well, a lot of flags were missing indeed, not only KLD_MODULE. As it turns
    out, you run the kernel stripped of each and any debugging support, without
    even INVARIANTS_SUPPORT. You also seem to have missed WERROR="" on make
    command line. Basically, you did everything what message in ~kan/xfs told
    you not to do ... and good thing you did :) I created a new snapshot file
    which should fix compilation on bare kernels like yours is.

    Keep in mind though that it is unlikely that I will be able to help you
    in case you stumble upon a panic in your config. 

    --
Alexander Kabaev
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
  • Next message: vladimir_at_math.uic.edu: "USB mouse problems (5.4 BETA); vmware port"

    Relevant Pages

    • Re: [BUG] linux-next: Tree for May 19/20/21 - BUG at arch/x86/kernel/io_apic_64.c:353!
      ... Can you include the config when you send these, ... from next report will send across the .config file also. ... for the kernel bug discussed. ... # PCI IDE chipsets support ...
      (Linux-Kernel)
    • Re: difficulty recompiling RHEL 4.2 kernel
      ... figures an as-yet-uncompiled kernel to the old, existing configuration, ... This can cause format changes in the .config file, ... It's a handy way to get a starting place for what drivers your current ...
      (comp.os.linux.setup)
    • Re: Locating Debian kernel .config
      ... >> of building a kernel with the stock Debian configuration. ... >> I've been unable to locate the .config file corresponding to ... > Anyhow, with the 2.6.8 kernel, at least, there is a "config" file ...
      (Debian-User)
    • Re: difficulty recompiling RHEL 4.2 kernel
      ... figures an as-yet-uncompiled kernel to the old, existing configuration, ... This can cause format changes in the .config file, ... It's a handy way to get a starting place for what drivers your current ...
      (comp.os.linux.setup)
    • SOLVED: New kernel unable to mount/see a whole HD
      ... kernel: getting rid of initrd. ... > config that you are currently using. ... Then save the new .config file. ...
      (Debian-User)