search for: dumping

...ev/nst0) in order to make some external backup..... I dump several filesystems (/, /boot /usr /var /home and others)....so and when I try to dump manualy for expmple /boot I get this: [root at Server ~]# dump -0vuf /dev/nst0 /boot DUMP: Date of this level 0 dump: Thu Sep 13 16:00:02 2007 DUMP: Dumping /dev/md0 (/boot) to /dev/nst0 DUMP: Excluding inode 8 (journal inode) from dump DUMP: Excluding inode 7 (resize inode) from dump DUMP: Label: none DUMP: Writing 10 Kilobyte records DUMP: mapping (Pass I) [regular files] DUMP: mapping (Pass II) [directories] DUMP: estimated 5706 blocks...

...inode 0 file (null) restore: Tape is not a dump tape I have another copy of the backup on another disk with the same checksum and it gets the same error as well. Here's a log file from when the backup was done back in 2009: DUMP: Date of this level 0 dump: Wed Apr 29 09:24:36 2009 ? DUMP: Dumping /dev/md1 (/u1) to u1_l0_04-29-09_md1.dump ? DUMP: Label: /u1 ? DUMP: Writing 10 Kilobyte records ? DUMP: Compressing output at compression level 2 (bzlib) ? DUMP: mapping (Pass I) [regular files] ? DUMP: mapping (Pass II) [directories] ? DUMP: estimated 95176885 blocks. ? DUMP: writing QFA p...

On 8/7/19 6:20 PM, Hiroshi Yamauchi wrote: > I basically run "clang > -fexperimental-new-pass-manager -print-after-all ..." > > It's conceivable that something is different in our setup or in clang > (from opt)... I'll see if I can reproduce it outside our setup. Does it depend on machine architecture? I generally use x86... regards,   Fedor. > > Thanks.

...t;parameter") # # Enter an environment number, or 0 to exit # Selection: 5 # Browsing in the environment with call: # .active-rstudio-document#9: f("parameter") # Called from: debugger.look(ind) # Browse[1]> g # [1] "global" # Browse[1]> while dumping to a file # Test script 2 g <- "global" f <- function(p) { l <- "local" dump.frames(to.file = TRUE, include.GlobalEnv = TRUE) } f("parameter") results in # > load("last.dump.rda") # > debugger() # Message: object '...

Dear R friends, to allow post-mortem debugging In my Rscript based batch jobs I use tryCatch( <R expression>, error = function(e) { dump.frames(to.file = TRUE) }) to write the called frames into a dump file. This is similar to the method recommended in the "Writing R extensions" manual in section 4.2 Debugging R code (page 96):

...icely! This could easily be morphed into the ''xm dump'' > command > >- it just > > didn''t occur to me at the time! > > > Your xendump command is dump feature without pause. > In the case without pause, domain''s memory is modified while dumping. > I think both w/o and w pause are needed. Hmm... perhaps although I''m not convinced -- I understand that memory can change during the dump and therefore there can be some inconsistencies in the dump, HOWEVER, pausing the domain doesn''t ensure all the data structures are cons...

Hi, In the case of linux, crash_kexec() is occured by "sysrq c". In the case of DomainU on xen, Help is occured by "sysrq c" now. So The way of dumping DomainU''s memory manualy is nothing. I fix this issue by the following way. 1. Panic is occured by "sysrq c" on both Domain0 and DomainU. 2. On DomainU, coredump is generated in /var/xen/dump (on Domain0). On Domain0, crash_kexec() is called by panic() if implemented. I test...

Hi, I am finding that my project that previously successfully built with versions 3.5 to 4.0 is now failing to link because of missing implementation for dump(). Errors I get are: Undefined symbols for architecture x86_64: "llvm::Type::dump() const", referenced from: ravi::LuaLLVMTypes::dump() in ravi_llvmtypes.cpp.o dump_content(lua_State*) in ravi_llvmluaapi.cpp.o

...his is only for crashing a domain. > If enable-dump is yes, we can get the domain''s core after crash. > And If we want to atomatically reboot, we should set > on_crash=''restart'' > in domain configuration. > > 2. xm dump > This is for live dumping a domain. > This implementation is: > 1. pause the domain > 2. dumping the domain > 3. unpause the domain > 4. reboot (if --noreboot option, don''t reboot) > > I think we want to reboot when we want to dump. > So I want to be default...

...restore: Tape is not a dump tape what does 'file' think the file is - i.e. what does file u1_l0_04-29-09_md1.dump say? > > > Here's a log file from when the backup was done back in 2009: > > DUMP: Date of this level 0 dump: Wed Apr 29 09:24:36 2009 > DUMP: Dumping /dev/md1 (/u1) to u1_l0_04-29-09_md1.dump > DUMP: Label: /u1 > DUMP: Writing 10 Kilobyte records > DUMP: Compressing output at compression level 2 (bzlib) > DUMP: finished in 23704 seconds, throughput 4075 kBytes/sec > DUMP: Date of this level 0 dump: Wed Apr 29 09:2...

...ugs.debian.org_2005_01_02 tags 706233 +patch thanks This is somewhat more FHS compliant IMHO. commit 7d171826bc97bf5f3f2019fc32c1ca85b49de7c9 Author: Ian Campbell <ijc at hellion.org.uk> Date: Fri Aug 16 14:54:42 2013 +0100 * debian/patches/tools-core-dump-dir.patch: Switch tools to dumping to /var/log/xen/dump by default. * debian/xen-utils-common.dirs: Ensure /var/lib/xen/dump is created * debian/changelog: Update * debian/patches/series: Add new patch diff --git a/xen/debian/changelog b/xen/debian/changelog index 6100e75..ace8ad4 100644 --- a/xen/debian/changelog...

I am trying to parse LLVM IR from a bit code file. I went through the following steps. hello.cpp #include <iostream> int main() { std::cout << "Hello world!" << "\n"; return 0;} dump.cpp #include <llvm/IR/Module.h>#include <llvm/IRReader/IRReader.h>#include <llvm/IR/LLVMContext.h>#include <llvm/Support/SourceMgr.h> using

tags 706233 +patch thanks This is somewhat more FHS compliant IMHO. commit 7d171826bc97bf5f3f2019fc32c1ca85b49de7c9 Author: Ian Campbell <ijc at hellion.org.uk> Date: Fri Aug 16 14:54:42 2013 +0100 * debian/patches/tools-core-dump-dir.patch: Switch tools to dumping to /var/log/xen/dump by default. * debian/xen-utils-common.dirs: Ensure /var/lib/xen/dump is created * debian/changelog: Update * debian/patches/series: Add new patch diff --git a/xen/debian/changelog b/xen/debian/changelog index 6100e75..ace8ad4 100644 --- a/xen/debian/changelog...

Hi, I would like to get a clear picture on external snapshots memory dump ( i.e. system-checkpoint) vs dumping the memory of the guest. I have created external snapshots which produces a disk file and a memory file. I am not able to use this memory file in any memory analysis tools, for instance volatility. However, the memory dump taken through "virsh dump" works just fine with such tools. What...

..., and a review of the log file claims all went well. Now for the restore... I just tried playing with different options of restore, but could not successfully restore anything. I ensured I was in a scratch area so as to hopefully not overwrite current files. What is the proper procedure for dumping and restoring now? Should I be dumping to /dev/nst0/dump? What restore commands would I use to recall a file? I'd like to keep things as simple as possible - people have suggested legato and amanda, but for now, I would think/hope dump and restore would work. Thanks. Scott

On 11/3/18 3:26 AM, Pete Biggs wrote: >> restore tvf u1_l0_04-29-09_md1.dump Verify tape and initialize maps >> Input is from a local file/pipe >> Checksum error 20311110402, inode 0 file (null) >> restore: Tape is not a dump tape > what does 'file' think the file is - i.e. what does > > file u1_l0_04-29-09_md1.dump u1_l0_04-29-09_md1.dump:?? data

...h the date it was executed. Right now, I manually edit the script to change the filename to the date the dump will be taken. To get a differential dump, would I have dump produce its output to the same file each time? I would not want to overwright the existing contents. I'm currently dumping to a file on an external hard drive, but will eventually go to tape. Thanks for feedback. Scott

I'm using the dump command to pass data to WinBUGS/OpenBUGS/JAGS and have run into a problem. Here is some R-code: foo <- array(1:6, dim=c(2,3)) dump('foo', file='dumpdata.R') dump('foo', file='dumpdata.R', append=TRUE, evaluate=TRUE) foo2 <- array(c(2,3,5,7,9,7,5,3), dim=c(2,4)) dump('foo2', file='dumpdata.R', append=TRUE) And here is

I have a couple C5 systems I want to back up. My plan is to, one way or another, back them up to a C5 machine in my office. I have samba installed on the systems to back up, the machines are mounted on the system in my office, and a tape library hanging of the system in my office. I was hoping to perform a simple /sbin/dump of the remote systems. I put together a script for another

Hi Martin, On 25 September 2017 at 20:35, Martin J. O'Riordan <MartinO at theheart.ie> wrote: > Are you building a Debug or Release version of the compiler? It seems that in Release builds of LLVM 5.0 the dump() implementation is absent, although the method is available in the interface. This is plain wrong in my view. If the dump() has to be removed then it should not be present