Bug#583870: inconsistencies in ext3 file systems
On 04/05/2012 12:09 AM, Jonathan Nieder wrote: Toni Müller wrote: the file system is still available, but I need to check with the user if I can ship his data offsite Did you find out? Yuck. I talked to the user, and he's fine with shipping the data, but somehow, it has become unclear which machine is effected, and furthermore, the user dislikes loss of operation to find out. I'll try to talk to him again to make the data finally available. Sorry for the delay. :(( Kind regards, --Toni++ -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f7cdace.3090...@oeko.net
Bug#583870: inconsistencies in ext3 file systems
On 11/29/2011 12:38 PM, Jonathan Nieder wrote: Jonathan Nieder wrote: Note that e2image -r only writes metadata (using holes in place of actual data), so e2image -r device - | bzip2 corrupted.e2i.bz2 may not be too large if the metadata is not too complex. If you want to avoid revealing filenames, the -s option to e2image can help. Now that I look at the manual more closely, e2image -Q might be more convenient. I don't see -Q mentioned in the man page. You mean, I should backport the e2image from Wheezy (where it first seems to appear) to Etch (the affected system)? Any gotchas that I should be aware of? Kind regards, --Toni++ -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4ed4c86b.3070...@oeko.net
Bug#583870: inconsistencies in ext3 file systems
Hi Jonathan, On 11/27/2011 05:06 AM, Jonathan Nieder wrote: Do you still have the corrupted filesystem available? It might be interesting to try to do a post-mortem analysis on it --- please see the RAW IMAGE FILES section of e2image(8) and let us know if that will be possible. the file system is still available, but I need to check with the user if I can ship his data offsite, and it would be a large file (~115GB). I have no way to store that image on the same machine, so it needs to be shipped elsewhere using nc or something, to begin with (iow, it could take some time to get done). Kind regards, --Toni++ -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4ed3ce91.2070...@oeko.net
Bug#623514: Hibernate problem
Hi, while I haven't conducted as many tests as Denis has, I can say that my T500 hibernated nicely up until 2.6.32 last version before -36 (I can't currently confirm for 2.6.32-36), and breaks for every later kernel. I can also say that, for the even more recent kernels, the machine does not even suspend-to-ram. I'm running the -686 variant of things, not the amd64 stuff. Feel free to ask any questions. Kind regards, --Toni++ -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4e7702f3.5090...@oeko.net
