xfs
[Top] [All Lists]
<prev [Date] next>
[Advanced]
 <prev [Thread] next>

Re: Fwd: Ecartis command results: appsub xfs greg.martyn@xxxxxxxxx 471AA

from [Justin Piszcz] [Permanent Link][Original]
To: Greg Martyn <greg.martyn@xxxxxxxxx>
Subject: Re: Fwd: Ecartis command results: appsub xfs greg.martyn@xxxxxxxxx 471AA1B0:62C8.1:ksf
From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
Date: Sun, 21 Oct 2007 04:12:34 -0400 (EDT)
Cc: xfs@xxxxxxxxxxx
In-reply-to: <6e0c99d0710201805k7ac77df0secce68307a76ca15@xxxxxxxxxxxxxx>
References: <ecartis-10202007180248.26524.2@oss> <6e0c99d0710201805k7ac77df0secce68307a76ca15@xxxxxxxxxxxxxx>
Sender: xfs-bounce@xxxxxxxxxxx 
Not a good message to see on a filesystem mailing list :(

On Sat, 20 Oct 2007, Greg Martyn wrote:


is this a serious message? :-p

---------- Forwarded message ----------
From: Ecartis <ecartis@xxxxxxxxxxx>
Date: Oct 20, 2007 9:02 PM
Subject: Ecartis command results: appsub xfs greg.martyn@xxxxxxxxx
471AA1B0:62C8.1:ksf
To: greg.martyn@xxxxxxxxx



List context changed to 'xfs' by following command.

appsub xfs greg.martyn@xxxxxxxxx 471AA1B0:62C8.1:ksf

Unable to process request due to filesystem error.

---
Ecartis v1.0.0 - job execution complete.
[More with this subject...]
<Prev in Thread] Current Thread [Next in Thread>
Previous by Date:  mount: /dev/md0: can't read superblock, Greg Martyn
Next by Date:  filesystem/disk paper seems to like XFS, Justin Piszcz
Previous by Thread:  Fwd: Ecartis command results: appsub xfs greg.martyn@xxxxxxxxx 471AA1B0:62C8.1:ksf, Greg Martyn
Next by Thread:  mount: /dev/md0: can't read superblock, Greg Martyn
Indexes:  [Date] [Thread] [Top] [All Lists]