search for: loopn

On Wed, 22 Oct 2008, Russell Coker wrote: > It seems reasonable to create a file /etc/modprobe.d/xen that contains > the following line to alleviate this: > options loop max_loop=32 Since kernel 2.6.22, loop devices are allocated dynamically, so that you can `mknod /dev/loopN b 7 N` for any N and start using it immediately. The max_loop option causes more loop devices to be preallocated, but also disables dynamic allocation. So maybe this problem is better solved by teaching /etc/xen/scripts/block to mknod a new loop device if it can?t find one free. Untested patc...

..., so I can dd it back onto my real /dev/md0 if need be. Alternatively, I can make a second copy of that backup file, use losetup on the second copy, and then experiment. Questions: 1. Is there any reason why I couldn't experiment with e2fsprogs binaries on a f/s dd image mounted over /dev/loopN? I.e., will it behave the same as a disk device as far as e2fsprogs are concerned? 2. If my assertion is correct that most of my f/s is intact but the journal is FUBAR, I need to find a way to force fsck to ignore the journal no matter what. Is there such a tool or option to some tool?...

...\ > --metadata=1.0 --layout=left-symmetric --chunk=64 --bitmap=none \ > /dev/md10 /dev/loop0 missing /dev/loop2 /dev/loop3 > > * Recover 99.9% of the data from /dev/md10. > Why not recover directly from backup? This saves time. From your last command why you inserted /dev/loopN? > One more hint for those interested: > Even with RAID1, I don't use the whole disk as one big RAID1. Instead, I > slice it into equally sized parts - not physically :-) - and create > multiple smaller RAID1 arrays on it. If a disk is 8TB, I create 8 > paritions of 1TB and then...

...v cx,64*1024/16 + call smp_scan_config + jne .smp_done + .smp_found: mov dword [di-4],'-smp' + .smp_done: pop es + jmp .done_cpuid + + smp_scan_config: + xor esi,esi + jmp .scan_first + .scan_lap: add si,16 + .scan_first: cmp dword [es:si],'_MP_' ; signature + .scan_loop: loopne .scan_lap + je ._mp_found + ret + + ._mp_found: inc cx ; we're going though loop instruction + ; one more time + cmp byte [es:si+8],1; length is expected to be 1 paragraph + jne .scan_loop + xor eax,eax + add al,byte [es:si+0] + add al,byte [es:si+1] + add al,byte [es:si...

...layout=left-symmetric --chunk=64 --bitmap=none \ >> /dev/md10 /dev/loop0 missing /dev/loop2 /dev/loop3 >> >> * Recover 99.9% of the data from /dev/md10. >> > > Why not recover directly from backup? This saves time. > From your last command why you inserted /dev/loopN? I that case, the owner of the NAS was a photographer who had all his past work on the NAS with no real backup :-( What I did in that case was to dump all data from all disks of the array to files. Then I made copies of the original dump files to work with them. I didn't want to touch the dis...

On 01/30/19 03:45, Alessandro Baggi wrote: > Il 29/01/19 20:42, mark ha scritto: >> Alessandro Baggi wrote: >>> Il 29/01/19 18:47, mark ha scritto: >>>> Alessandro Baggi wrote: >>>>> Il 29/01/19 15:03, mark ha scritto: >>>>> >>>>>> I've no idea what happened, but the box I was working on last week

Hi All, I have several Xen virtual machines within logical volumes using LVM2. I did not use disk images for performance reasons. Conventionally, if I want to clone my virtual machines, I have to dd the LV to an image file. But this consumes a lot of time and harddisk space. So, instead of doing that, I want to use losetup and kpartx with my logical volumes, which contain operating systems of

..._GP_cPt_V4: >> + case Hexagon::STriw_GP_cNotPt_V4: >> + case Hexagon::STriw_GP_cdnPt_V4: >> + case Hexagon::STriw_GP_cdnNotPt_V4: >> + return QRI->Subtarget.hasV4TOps(); >> + } >> + return false; >> +} >> + >> +static bool IsLoopN(MachineInstr *MI) { >> + return (MI->getOpcode() == Hexagon::LOOP0_i || >> + MI->getOpcode() == Hexagon::LOOP0_r); >> +} >> + >> +/// DoesModifyCalleeSavedReg - Returns true if the instruction modifies a >> +/// callee-saved register. >> +st...