<html><head></head><body>Still the same outage from 2 weeks ago, Stan; my script had nothing to do with breaking the FSs. Was a zorched power supply, almost certainly. <br>
<br>
And in fact, after 32 years adminning *nix boxes for a living, yes, I do expect that if any userland program can /corrupt/ FS internals without twiddling with /dev/sdX, either the FS is broken or the hardware is.<br>
<br>
In this case I'm quite certain it /was/ the hardware, and 85-90% confident it's fixed now.<br>
<br>
Cheers,<br>
-jra<br>
-- <br>
Sent from my Android phone with K-9 Mail. Please excuse my brevity.<br><br><div class="gmail_quote">Stan Hoeppner <stan@hardwarefreak.com> wrote:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<pre style="white-space: pre-wrap; word-wrap:break-word; font-family: monospace">On 8/18/2013 4:38 PM, Jay Ashworth wrote:<br />> I'm trying to dedupe the two large XFS filesystems on which I have DVR <br />> recordings, so that I can walk around amongst the available HDDs and create<br />> new filesystems under everything.<br />> <br />> Every time I rm a file, the filesystem blows up, and the driver shuts it<br />> down. <br />> <br />> Some background:<br />> <br />> At the moment, I have 2 devices, /dev/sdd1 mounted on /appl/media4, and<br />> /dev/sda1 mounted on /appl/media5, and a large script, created by hand-<br />> hacking the output of a perl dupe finder script.<br />> <br />> The large script was mangled so that it would remove anything that was a <br />> dupe from media4, unless the file was an unlabeled lost+found on media5,<br />> and had a name on media4. In that case, I removed the file on media5, and<br />>
; then
moved it from media4 to media5.<br />> <br />> After the hand-hacking on the script, I sorted it to do all the rm's first,<br />> and then all the mv's, to make sure free space when up before it went down.<br />> <br />> And, of course, when I ran the script, it caused the XFS driver to cough and<br />> die, leading to error 5s and gnashing of teeth.<br /><br />If this script is the catalyst of your XFS problems, it seems logical<br />that you would include said script in your trouble report, yet you did<br />not. It's a bit foolish to assume you can't break a Linux subsystem<br />with a poorly written program and/or in combination with a platform that<br />isn't up to the task being asked of it. As Joe mentioned having too<br />little RAM could be part of this problem.<br /><br />-- <br />Stan<br /><br /><br /></pre></blockquote></div></body></html>