Your message dated Thu, 05 Jun 2008 09:04:20 +1000
with message-id <[EMAIL PROTECTED]>
and subject line 
has caused the Debian Bug report #482053,
regarding xfsprogs: xfs_growfs will create unmountable filesystem on 32bit OS
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)


-- 
482053: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=482053
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: xfsprogs
Version: 2.8.11-1
Severity: critical
Justification: breaks the whole system

XFS on 32bit Linux cannot mount filesystems >16T see:
http://oss.sgi.com/archives/xfs/2008-01/msg00124.html

xfs_grow will grow a filsystem larger than this which will function
untill the system is rebooted, at which point the filsystem becomes
inaccessable.  The resultant filesystem is readable on 64bit
architectures. 

xfs_growfs should at least warn of this condition, possibly it should
refuse to to grow filesystems over 16T on 32bit architectures.



-- System Information:
Debian Release: 4.0
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: i386 (i386)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18.8-csail
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)

Versions of packages xfsprogs depends on:
ii  lib 2.3.6.ds1-13etch5                    GNU C Library: Shared libraries
ii  lib 5.2-2                                GNU readline and history libraries
ii  lib 1.39+1.40-WIP-2006.11.14+dfsg-2etch1 universally unique id library

xfsprogs recommends no packages.

-- no debconf information



--- End Message ---
--- Begin Message ---
This problem was resolved in the XFS growfs code in the kernel,
so closing out this bug now.

cheers.

-- 
Nathan



--- End Message ---

Reply via email to