The preparations for d-i rc1 have started, so the beta2 release is now
broken. This is because every d-i image that obtains components from
the network (rather than e.g. a CD) relies on certain versions of
packages to be available in the Debian archive, and those versions are
no longer available
* Eric Sandeen [EMAIL PROTECTED] [2008-10-17 09:15]:
If you unmount remount, does the ls work then?
I cannot even mount it:
debian:~# mkfs.xfs -f /dev/sda5
meta-data=/dev/sda5 isize=256agcount=4, agsize=94380 blks
= sectsz=512 attr=2
data =
I tried xfs both on the old and new ABI.
(my first try was Jan 2008, old ABI)
ASAIR at kernel version 2.6.18
On Fri, 2008-10-17 at 11:46 +0200, Gaudenz Steinlin wrote:
On Fri, Oct 17, 2008 at 09:01:09AM +0200, Martin Michlmayr wrote:
* Eric Sandeen [EMAIL PROTECTED] [2008-10-16 17:13]:
So
Martin Michlmayr wrote:
* Eric Sandeen [EMAIL PROTECTED] [2008-10-17 09:15]:
Do you know what cachepolicy you're booted with? If it's writeallocate,
you might try cachepolicy=writeback, otherwise try cachepolicy=uncached
(which will be horribly slow) and see if the problem goes away or not;
On Sat, Oct 18, 2008 at 10:48:53PM +0300, Kirill A. Shutemov wrote:
Our team have experience with XFS on ARM OABI on NAS. It worked fine on
2.6.12, but got broken on 2.6.17.
So any chance to bisect it down to at least a kernel release where it
stopped working?
--
To UNSUBSCRIBE, email to
On Sat, Oct 18, 2008 at 10:57:56AM +0200, Martin Michlmayr wrote:
* Eric Sandeen [EMAIL PROTECTED] [2008-10-17 09:15]:
If you unmount remount, does the ls work then?
I cannot even mount it:
debian:~# mkfs.xfs -f /dev/sda5
meta-data=/dev/sda5 isize=256agcount=4,
Dave Chinner wrote:
On Sat, Oct 18, 2008 at 10:57:56AM +0200, Martin Michlmayr wrote:
* Eric Sandeen [EMAIL PROTECTED] [2008-10-17 09:15]:
If you unmount remount, does the ls work then?
I cannot even mount it:
debian:~# mkfs.xfs -f /dev/sda5
meta-data=/dev/sda5 isize=256
* Dave Chinner [EMAIL PROTECTED] [2008-10-19 12:48]:
That's the log replay indicating that there's a bad transaction
header in the log. Very strange - it shoul dbe a clean log. What
does xfs_logprint -t /dev/sda5 tell you about the transactions
in the log?
mdebian:~# mkfs.xfs -f /dev/sda5
8 matches
Mail list logo
