From: Stefan Pfetzing <dreamind@dreamind.de>
To: jsoe0708@tiscali.be
Cc: parisc-linux@lists.parisc-linux.org
Subject: [parisc-linux] Re: mkfs.xfs (xfsprogs-2.3.5) failled
Date: Thu, 24 Oct 2002 19:58:02 +0200 [thread overview]
Message-ID: <20021024175802.GA9490@dreamind.de> (raw)
In-Reply-To: <3DB5776100000362@ocpmta8.be.tiscali.com>
* jsoe0708@tiscali.be <jsoe0708@tiscali.be> [021023 09:30]:
> Hi Stephan,
>
> As you do earlier, I build a xfs-kernel diff versus 2.4.19 vanilla kernel,
> apply it against 2.4.19-pa22 (with very small problem) and obtain a bootable
> (and operational) kernel.
Yup.
> Now I rebuild debian package of xfsprogs-2.3.5 (cvs form) and obtain tools
> binaries (without warning or error) but even mkfs -t xfs (mkfs.xfs) failed
> with this concise message: "mkfs.xfs: cannot reserve space [28 - No space
> left on device]".
> (I try to xfs_check which failed also with a lot of error messages).
Yea thats a problem, still in the Linux/Parisc kernel. It gives garbage with
BLKGETSIZE64. Simply look in the xfslibs directory where BLGKETSIZE64 is used
and comment that out. Thats a disgusting hack but it leads to a set of working
xfsprogs.
If you want I can make a patch for you, but this will take some time, since I
have the source not right by hand now.
bye
Stefan
--
http://www.dreamind.de/
Oroborus and Debian GNU/Linux Developer.
next prev parent reply other threads:[~2002-10-24 17:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-23 7:30 [parisc-linux] mkfs.xfs (xfsprogs-2.3.5) failled jsoe0708
2002-10-24 17:58 ` Stefan Pfetzing [this message]
2002-10-24 18:15 ` [parisc-linux] " Randolph Chung
2002-10-24 18:17 ` Stefan Pfetzing
2002-10-24 19:00 ` Randolph Chung
2002-10-24 23:08 ` Stefan Pfetzing
2002-10-25 6:04 ` jsoe0708
2002-10-25 12:58 ` jsoe0708
2002-10-25 15:09 ` jsoe0708
2002-10-26 17:39 ` Joel Soete
2002-10-26 21:18 ` Randolph Chung
[not found] ` <3DBB30C0.6060000@freebel.net>
2002-10-27 0:32 ` Joel Soete
2002-10-26 23:40 ` Joel Soete
2002-10-25 15:26 ` Randolph Chung
2002-10-25 5:57 ` jsoe0708
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20021024175802.GA9490@dreamind.de \
--to=dreamind@dreamind.de \
--cc=jsoe0708@tiscali.be \
--cc=parisc-linux@lists.parisc-linux.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox