Robert Persson schreef: > Has anyone else had a problem in which reiser4 loses a file, but fsck.reiser4 > can't find anything wrong? > > I was trying to burn a large file to dvd+rw but k3b would just ignore it. It > would therefore spend very little time writing the dvd, but a long time > verifying it before it decided that the file was missing from the dvd. > > I then found that when I clicked on the file icon in konqueror I would get a > message that the file did not exist, while khexedit would show me an empty > file. > > F3ing in midnight commander would also show me an empty file until the file > was moved to trash, after which it would show me the binary gibberish I would > normally have expected. However moving the file to trash did not help > konqueror or khexedit to see anything in the file. > > I booted from a rescue disk and ran fsck.reiser4, but it found no error. > > The file had a simple ascii name (winxp.img) and, at 4GB exactly, was by far > the largest file I have ever had on my reiser4 partition. > > Deleting the file completely freed up the space the file was supposed to have > been taking up. > > Does anyone know if this is a known problem with reiser4, if it is indeed a > problem particularly with large files, and if I would be likely to meet it > again once I start using large files more often for video editing and stuff? > > Many thanks > Robert > > PS If I don't reply promptly to your replies this time it's not because I'm > being rude. I'm just going to be off-grid for a little while.
Are you sure this is a reiser4 problem and not a K3b limitation? I have found that K3b will not properly burn data CDs over about 2GB (*.iso files converted to CD are fine, I just mean for example a *.mpg or some such burned as data). I'm using Reiser 3, but I never thought that Reiser itself was the problem.... I found that K3b would *claim* that it burned the DVD (+R for me), but the DVD was actually unreadable by any means under Linux (it could be read under Windows). I don't remember if Nero for Linux exhibited the same problem or not. IIrc, it *might* work properly if you tar or tar.gz the files first, it's just that a single pure data file above a certain size seems to bork the whole thing. Plus, is there a reason that you're burning an *.img as a data file? This is usually another sort of compressed archive similar to *.iso, and if K3b doesn't detect it natively in the "Burn CD image" dialog (although I think it does), Nero for Linux definitely will. Anyway, hope this info is of some use to you. I have no experience with Reiser 4, so you might be right, but based on my experience with K3b (and the fact that Reiser is not showing any problems on its own account), there could easily be another reason for this. And sorry if somebody else said this already; the lack of subjects means I'd have to go through every unread message just to see if somebody else answered, and I was impatient :) . Holly -- [email protected] mailing list
