search for: recovered

Hello, When I look at email files on my server (mdbox format), they contain random LZ4 stuff. I have now changed the compression to gzip and new mails look cleaner. But older ones have problems. A mail file looks like this: 2 M1e C5655b6a8 ^A^BN 00000000000006F4 Dovecot-LZ4^M*<9B><C5>^@^A^@^@^@^@^F<DD><FF><83>Return-path: <nobody at

Hi, recover() sends all its messages, which I consider to be error messages, to stdout. I think they more properly belong to stderr. This is an important difference for those of us who use R in batch mode to generate ASCII files. Thanks, Vadim [[alternative HTML version deleted]]

...er that we have found that SOME files disappeared (they are not seen in the directories where they have been before). The data are extremely important and contain a lot of programs, scripts for some data analysis and very hard to recover by hands. I have run ''fsck -y" once more and it recovered just few files.. Is there any way, any tool that would allow to recover the data? Probably there is some specific options for the recovery ralated with journaling in ext3? I have used debugfs, it produced following, if it helps: debugfs: open -f -w /dev/sdb1 debugfs: features Filesystem features...

For years I have been using options(error = recover) either in .Rprofile or from within R for debugging purposes. The functionality of this appears to have changed and I can't recover it (no pun intended) using the ?options help page. How can I get the old functionality back, particularly from within .Rprofile? A specific line entry would be appreciated. An example, the help page, and

After using options(error=recover), it takes a long time (too long) to get back to the prompt. Look at: Browse[1]> recover() Enter a frame number, or 0 to exit 1: window(test, start = c(15, 1), end = c(17, 1), extend = TRUE) 2: window.ts(test, start = c(15, 1), end = c(17, 1), extend = TRUE) 3: as.ts(window.default(x, ...)) 4: window.default(x, ...) 5: function () 6: eval(quote(browser()),

I'd like to be able to set options(error=recover) in my Rprofile.site file. When I do this I get the message "Error in options(error = recover) : object "recover" not found I assume this is because the utils package (where recover and dump.frames are defined) has not been loaded at the time I make this call. I suppose I could explicitly do library("utils") before

Still looking for a Recover data Mac (http://www.umacos.com/data-recovery-mac.html) which supports storage media like ,usb flash drives, external hard drives, memory cards. Be compatible with portable device:mp3/mp4 player. And supports Mac OS X 10.3 or later. I highly recommend you this one to . Recover data Mac is the best data recovery software on the market for recovering data from a

Hello, I've noticed that Rscript didn't exit with error code if I set options error = utils::recover in .Rprofile . for example Rscript -e "asdf" Error: object 'asdf' not found No suitable frames for recover() echo $? 0 if didn't set options in .Rprofile, Rscript exit with error code 1, is this expected behavior ?

Thanks for explanation, so recover in non-interactive session exit with 0 is expected behavior . dump.frames said that it always write to file (workspace , or specified file). I have a R script run as a auto build stage, so I want to print detail backtrace to console (with source file, line number) for quickly debug, without saving any dump. I tried options(error=

...from an earlier sysadmin who left the company & nobody know what's what. I need to recover data so I need to backup each of the disks to a disk image file first, then find block-size/recover lvm metadata on the volume, mount the volume to my current server and recover whatever files can be recovered manually. My question is: - what switches to be used with dd in creating the image, so that I retain the lvm disk data, for future recovery, if I mess up the recovery job? Can you please give the actual command assuming disk is connected at /dev/sdb? - How do I find the blocksize used by the dis...

Hi! I'm doing Monte Carlo analyses of the distribution of the t-statistics of the parameters of models evaluated with the lm( ) function. Is there an easy way to recover the t-statistics (similarly to using coef to recover the coefficients)? Thanks, joseph --------------------------------- [[alternative HTML version deleted]]

I have 10 servers in a cluster running Debian Etch with 2.6.26-bpo.2 with a backport of ocfs2-tools-1.4.1-1 I'm using AoE to export the drives from a Debian Lenny server in the cluster. My problem is if I mount the ocfs2 partition on the server that is exporting it via AoE it fences the entire cluster. Looking at the logs exporting the ocfs2 partition doesn't give much information...

Hi, I'd like to try using "options(error=recover) in my ~/.Rprofile, but it appears that the function "recover" is not defined during R startup when the .Rprofile is processed. "recover" is defined after I get an R prompt, however. Can anyone shed light on why this is, and whether a work-around is possible? I've tested this on a variety of systems

In the current recovery procedure, recovering node recovers orphans from the slot it is holding and the slots that dead nodes were holding. Other online nodes recover orphans from their slots. But orphans in offline slots are left un-recovered. This patch queues recovery_completion for offline slots. Signed-off-by: Srinivas Eeda <srinivas.eeda at oracle.com> --- fs/ocfs2/journal.c | 21 ++++++++++++++++----- 1 files changed, 16 insertions(+), 5 deletions(-) diff --git a/fs/ocfs2/journal.c b/fs/ocfs2/journal.c index 71b2ea4..5...

Any recommendations for tools to diagnose and recover problems on an ext4 file system? In particular: root@jessie01:~# mount -o ro /dev/markov02/root /mnt/markov02 mount: wrong fs type, bad option, bad superblock on /dev/mapper/markov02-root, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so. and e2fsck

Currently we only queue recovery during mount if the journal is dirty. If the last node holding orphans in other node's orphan directory dies and is the first one to mount then it only recovers its orphan directory which leaves the orphans in other nodes slots. Since the other nodes journals are clean they will not queue to recover their orphan directory. This patch queues to recover orphans

Hello All, I was curious to know if there is any method for recovering data that has been deleted by a user on accident, this occurred prior to the running of the official back-up. Anyway, a user ended up losing a few hours of work, so I need to attempt to recover what I can, if at all possible. Any suggestions? Regards, Robert Adkins II IT Manager/Buyer Impel Industries, Inc. 586-254-5800

So I''m writing my (dis)adventure with btrfs here hoping to help the developers or someone with similar problems. I had a btrfs filesystem at work, using two 1TB disks, raid1 for both data and metadata. A week ago one of the two disks start having hundreds of relocated sectors, so I decide to change it. I remove the failing disk, mount with -o degraded and every works fine. The day later

...ion (while data is been undated), ZFS keeps a copy of the previous data. However, once the transaction is successfully completed, isn''t it the case that the previous data blocks are unreferenced and can be used by future writes? So there should be no guarantee that the previous data can be recovered. Thanks This message posted from opensolaris.org

Hello, When using recover, the called from information is always "eval(expr, envir, enclos)", which is not particularly useful. > f <- function( ){ g <- function(){ stop( "ouch") }; g() } > options( error = recover ) > f() Error in g() : ouch Enter a frame number, or 0 to exit 1: f() 2: g() Selection: 1 Called from: eval(expr, envir, enclos) I'm