[opensuse] Repair of XFS fails
I'm slowly working my way though putting my DVDs on to disk and hence USB so I can watch them on my tablet. For the most part I use handbrake. Nice UI. Some DVDs, though, handbrake doesn't seem to want to deal with. Some DVDs take it like that; I don't now why. I was stuck in a recent movie, "Jurassic World". it a 2hr, 5 min movie. Handbrake scans it and then ... nothing. So I turn to VLC, which ... well it play the menu. I set VLC to rip the mive. it rips that one part, the menu, over and over and over. It never modes past it. So I break out of VLC and delete the 3.6M, just grown to 3.7 ... 3.8 ov that over-and-over but not the main movie. I try VLC again but with a starting point of "1" rather than "0". It hangs. It hangs the whole machine. Rebook I get an error. Its the mounted ~/MyMovies, which is an XFS. Oh, <deleted>!. There goes this mornings work. I try xfs_repair with a few options such as verbose, progressively more aggressive about it. Xfs_repair says its all OK. Mounting says: mount: wrong fs type, bad option, bad superblock on /dev/mapper/vgmain-MyMovies, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so. That's a pretty standard message. The dmesg|tail says [ 4475.435209] XFS (dm-20): Mounting V5 Filesystem [ 4475.489498] XFS (dm-20): Corruption warning: Metadata has LSN (1:5500) ahead of current LSN (1:2). Please unmount and run xfs_repair (>= v4.3) to resolve. [ 4475.489503] XFS (dm-20): log mount/recovery failed: error -22 [ 4475.489537] XFS (dm-20): log mount failed Iterating xfs_repair & mount is of no joy. I'd chose XFS on advice here to deal with big files, aka movies. I'm not happy with the result I've ended up with. Is there anyone more knowledgeable about XFS recovery? -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Thu, 25 Aug 2016 15:34:42 -0400 Anton Aylward <opensuse@antonaylward.com> wrote:
I'm slowly working my way though putting my DVDs on to disk and hence USB so I can watch them on my tablet.
For the most part I use handbrake. Nice UI.
Some DVDs, though, handbrake doesn't seem to want to deal with. Some DVDs take it like that; I don't now why.
I was stuck in a recent movie, "Jurassic World". it a 2hr, 5 min movie. Handbrake scans it and then ... nothing.
So I turn to VLC, which ... well it play the menu. I set VLC to rip the mive. it rips that one part, the menu, over and over and over. It never modes past it. So I break out of VLC and delete the 3.6M, just grown to 3.7 ... 3.8 ov that over-and-over but not the main movie.
I try VLC again but with a starting point of "1" rather than "0".
It hangs. It hangs the whole machine. Rebook I get an error. Its the mounted ~/MyMovies, which is an XFS. Oh, <deleted>!. There goes this mornings work.
I try xfs_repair with a few options such as verbose, progressively more aggressive about it. Xfs_repair says its all OK. Mounting says:
mount: wrong fs type, bad option, bad superblock on /dev/mapper/vgmain-MyMovies, missing codepage or helper program, or other error
In some cases useful info is found in syslog - try dmesg | tail or so.
That's a pretty standard message. The dmesg|tail says
[ 4475.435209] XFS (dm-20): Mounting V5 Filesystem [ 4475.489498] XFS (dm-20): Corruption warning: Metadata has LSN (1:5500) ahead of current LSN (1:2). Please unmount and run xfs_repair (>= v4.3) to resolve. [ 4475.489503] XFS (dm-20): log mount/recovery failed: error -22 [ 4475.489537] XFS (dm-20): log mount failed
Iterating xfs_repair & mount is of no joy.
I'd chose XFS on advice here to deal with big files, aka movies. I'm not happy with the result I've ended up with.
Is there anyone more knowledgeable about XFS recovery?
There are loads of people extremely knowledgeable about it on the XFS mailing list. I suggest trying there. FWIW I haven't had any problems with XFS in years and years of using it, so hopefully they'll get to the bottom of the problem. Cheers, Dave -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2016-08-25 23:24, Dave Howorth wrote:
On Thu, 25 Aug 2016 15:34:42 -0400 Anton Aylward <> wrote:
Iterating xfs_repair & mount is of no joy.
I'd chose XFS on advice here to deal with big files, aka movies. I'm not happy with the result I've ended up with.
Is there anyone more knowledgeable about XFS recovery?
There are loads of people extremely knowledgeable about it on the XFS mailing list. I suggest trying there. FWIW I haven't had any problems with XFS in years and years of using it, so hopefully they'll get to the bottom of the problem.
Same recommendation here. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
On Thu, Aug 25, 2016 at 3:24 PM, Dave Howorth <dave@howorth.org.uk> wrote:
On Thu, 25 Aug 2016 15:34:42 -0400 Anton Aylward <opensuse@antonaylward.com> wrote:
That's a pretty standard message. The dmesg|tail says
[ 4475.435209] XFS (dm-20): Mounting V5 Filesystem [ 4475.489498] XFS (dm-20): Corruption warning: Metadata has LSN (1:5500) ahead of current LSN (1:2). Please unmount and run xfs_repair (>= v4.3) to resolve. [ 4475.489503] XFS (dm-20): log mount/recovery failed: error -22 [ 4475.489537] XFS (dm-20): log mount failed
Iterating xfs_repair & mount is of no joy.
I'd chose XFS on advice here to deal with big files, aka movies. I'm not happy with the result I've ended up with.
Is there anyone more knowledgeable about XFS recovery?
There are loads of people extremely knowledgeable about it on the XFS mailing list. I suggest trying there. FWIW I haven't had any problems with XFS in years and years of using it, so hopefully they'll get to the bottom of the problem.
The XFS list will want a good report and the above is missing some information: http://xfs.org/index.php/XFS_FAQ#Q:_What_information_should_I_include_when_r... In addition to that, they will want to see the kernel messages leading up to the problem. I would find the boot where things were working and then went bad, and include that entire boot, filtered for kernel messages: journalctl -b -1 (or -2, -3) will get you previous boots. And filter with -k like this journalctl -b -1 -k > kernel.log And include that file as an attachment. The first traces are at least as important as the most recent. Don't think it's helpful to trim it, often the actual instigator is before the file system starts complaining, so include the whole thing. Next, what was done to the file system following the problem. Reboot? xfs_repair? mount? Be specific. XFS doesn't like having xfs_repair run on it right away after a reboot, it wants to just be mounted. And also provide a complete history of "iterating xfs_repair & mount" with all of the messages. The more information provided, the better the chance of recovery. Also include what this file system is built on top of. I see XFS (dm-20) so that suggests it's on LVM or maybe dmcrypt. -- Chris Murphy -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (4)
-
Anton Aylward -
Carlos E. R. -
Chris Murphy -
Dave Howorth