On Fri, Jan 21, 2005 at 04:09:15PM +0100, Walter Hofmann wrote:
> On Fri, 21 Jan 2005, Theodore Ts'o wrote:
>
> > I've investigated the file you sent me, and it was very helpful
> > indeed, thanks. What is going on is that when a filesystem is resized
> > enough so that we need to move the inode
On Fri, 21 Jan 2005, Theodore Ts'o wrote:
> I've investigated the file you sent me, and it was very helpful
> indeed, thanks. What is going on is that when a filesystem is resized
> enough so that we need to move the inode table, we reserve both the
> old and new locations of the inode table. Ho
On Thu, Jan 20, 2005 at 11:59:11AM +0100, Walter Hofmann wrote:
> Dear Ted,
>
> I have now finished preparing the image file you requested. It is
> attached to this mail. I have a number of remarks:
>
> - the output of e2image was one byte longer than the device -- I think
> you need to remov
On Wed, 19 Jan 2005, Theodore Ts'o wrote:
> Oh, instead of waiting for the Debian mirrors to propagate, you could
> also download the e2fsprogs 1.36-rc2 sources, and then apply the
> following patch...
I took e2fsprogs and -libs from incoming.debian.org. It's currently
creating the image. I hope
Oh, instead of waiting for the Debian mirrors to propagate, you could
also download the e2fsprogs 1.36-rc2 sources, and then apply the
following patch...
But, I think I will need the e2image dump in order to figure out what
happened. Thanks!!
- Ted
I've looked some more at the information you sent me, and it's not
enough to track it down. I can tell that the filesystem had been
resized at least once or twice before, and this seems to be related to
an inode table being moved, but that's about it.
So I've developed a patch to e2image that wil
On Tue, Jan 18, 2005 at 11:10:28AM +0100, Walter Hofmann wrote:
> Hi Ted,
>
> I have tried to rename the files & make an image for you. However, there
> where far to many fragments of old files and filenames left in the image
> file (probably in unused parts of directories), so I cannot sent thi
Hi Ted,
I have tried to rename the files & make an image for you. However, there
where far to many fragments of old files and filenames left in the image
file (probably in unused parts of directories), so I cannot sent this to
you. (BTW the image was 12MB and running it through bzip2 a second t
On Mon, Jan 17, 2005 at 10:45:59PM +0100, Walter Hofmann wrote:
> I have a backup, so I could theoretically do as you say. However: I
> would have to rename the directories. Will renaming all files to random
> names (of the same length, say) disturb the filesystem structure enough
> to make the
On Mon, 17 Jan 2005, Theodore Ts'o wrote:
> On Mon, Jan 17, 2005 at 04:25:46PM +0100, Walter Hofmann wrote:
> > Package: e2fsprogs
> > Version: 1.36rc2-1
> > Severity: normal
> >
> > I'm not sure how severe this is, but I e2fsck'ed a filesystem just after
> > resizing it and got some bitmap error
On Mon, Jan 17, 2005 at 04:25:46PM +0100, Walter Hofmann wrote:
> Package: e2fsprogs
> Version: 1.36rc2-1
> Severity: normal
>
> I'm not sure how severe this is, but I e2fsck'ed a filesystem just after
> resizing it and got some bitmap errors. Below is a screendump of the
> whole session.
> The fi
Package: e2fsprogs
Version: 1.36rc2-1
Severity: normal
I'm not sure how severe this is, but I e2fsck'ed a filesystem just after
resizing it and got some bitmap errors. Below is a screendump of the
whole session.
The filesystem is on /dev/loop0 (cryptoloop).
Walter
[EMAIL PROTECTED]:/usr/local/l
12 matches
Mail list logo
