Bug#535452: resize2fs fails to read mountpoint for online resize

2009-07-06 Thread Theodore Tso
On Thu, Jul 02, 2009 at 08:14:29PM +0200, Goswin von Brederlow wrote: OK, I see what's going on. We're freeing the mountpoint information so when we print it in an error message, the error message is getting printed as garbage. This probably doesn't qualify as a severity important level

Bug#535452: resize2fs fails to read mountpoint for online resize

2009-07-02 Thread Goswin Brederlow
Package: e2fsprogs Version: 1.41.7-1 Severity: important File: /sbin/resize2fs Hi, when I try to resize a filesystem I get: % resize2fs -p /dev/s/unseen resize2fs 1.41.7 (29-June-2009) Filesystem at /dev/s/unseen is mounted on ยท+; on-line resizing required old desc_blocks =

Bug#535452: resize2fs fails to read mountpoint for online resize

2009-07-02 Thread Theodore Tso
On Thu, Jul 02, 2009 at 12:03:10PM +0200, Goswin Brederlow wrote: Package: e2fsprogs Version: 1.41.7-1 Severity: important File: /sbin/resize2fs Hi, when I try to resize a filesystem I get: % resize2fs -p /dev/s/unseen resize2fs 1.41.7 (29-June-2009) Filesystem at

Bug#535452: resize2fs fails to read mountpoint for online resize

2009-07-02 Thread Goswin von Brederlow
Theodore Tso ty...@mit.edu writes: On Thu, Jul 02, 2009 at 12:03:10PM +0200, Goswin Brederlow wrote: Package: e2fsprogs Version: 1.41.7-1 Severity: important File: /sbin/resize2fs Hi, when I try to resize a filesystem I get: % resize2fs -p /dev/s/unseen resize2fs

Bug#535452: resize2fs fails to read mountpoint for online resize

2009-07-02 Thread Theodore Tso
severity 535452 normal tags 535452 +pending thanks OK, I see what's going on. We're freeing the mountpoint information so when we print it in an error message, the error message is getting printed as garbage. This probably doesn't qualify as a severity important level bug (a bug which has a

Bug#535452: resize2fs fails to read mountpoint for online resize

2009-07-02 Thread Goswin von Brederlow
Theodore Tso ty...@mit.edu writes: severity 535452 normal tags 535452 +pending thanks OK, I see what's going on. We're freeing the mountpoint information so when we print it in an error message, the error message is getting printed as garbage. This probably doesn't qualify as a severity