search for: blocknumber

...o a remove a loop which looks something like this: for 2 to number of rows in a matrix do{ if indextrow-1 is < currentIndexRow then do something. } My R code: for (i in 2:length(tUnitsort$Hour)){ ifelse(tUnitsort[i,4]>=tUnitsort[i-1,4],(tempMC =tUnitsort[i,7]),tempMC ) #col. 4 = BlockNumber; note tests to see if the offers have change to the next set of blocks. ifelse(tUnitsort[i,4]>=tUnitsort[i-1,4],(tempAC =tUnitsort[i,7]-(tUnitsort[i,8]-tUnitsort[i,9])),tempAC ) tUnitsort$MC[i] <- tempMC tUnitsort$AC[i] <- tempAC tUnitsort$PercentofMC[i] <- tUni...

...SelectionDAG/SelectionDAGISel.cpp b/lib/CodeGen/SelectionDAG/SelectionDAGISel.cpp index 58f029fbe9fc..7ee06fc153b2 100644 --- a/lib/CodeGen/SelectionDAG/SelectionDAGISel.cpp +++ b/lib/CodeGen/SelectionDAG/SelectionDAGISel.cpp @@ -659,7 +659,7 @@ void SelectionDAGISel::CodeGenAndEmitDAG() { (void)BlockNumber; bool MatchFilterBB = false; (void)MatchFilterBB; #ifndef NDEBUG - MatchFilterBB = (!FilterDAGBasicBlockName.empty() && + MatchFilterBB = (FilterDAGBasicBlockName.empty() || FilterDAGBasicBlockName == FuncInfo->MBB->getBasicBlock()-&gt...

...SelectionDAG/SelectionDAGISel.cpp b/lib/CodeGen/SelectionDAG/SelectionDAGISel.cpp index 58f029fbe9fc..7ee06fc153b2 100644 --- a/lib/CodeGen/SelectionDAG/SelectionDAGISel.cpp +++ b/lib/CodeGen/SelectionDAG/SelectionDAGISel.cpp @@ -659,7 +659,7 @@ void SelectionDAGISel::CodeGenAndEmitDAG() { (void)BlockNumber; bool MatchFilterBB = false; (void)MatchFilterBB; #ifndef NDEBUG - MatchFilterBB = (!FilterDAGBasicBlockName.empty() && + MatchFilterBB = (FilterDAGBasicBlockName.empty() || FilterDAGBasicBlockName == FuncInfo->MBB->getBasicBlock()-&gt...

...e following is the mailing list exchange: On 09/18/2014 07:01 PM, Robert Nichols wrote: > On 09/18/2014 12:37 PM, jd1008 wrote: >> Is there any other tool that can extract files from a partition that >> seems to have corrupted superblocks? >> I tried dumpe2fs, and fsck -b <blockNumber> >> to no avail. Tried all available block numbers that are listed >> when original mkfs was done, and it's output was saved. >> >> None of the blocks seem to work - all of them have invalid magic. > > Verify that the partition table still appears to be correct....

...exchange: > > > On 09/18/2014 07:01 PM, Robert Nichols wrote: >> On 09/18/2014 12:37 PM, jd1008 wrote: >>> Is there any other tool that can extract files from a partition that >>> seems to have corrupted superblocks? >>> I tried dumpe2fs, and fsck -b <blockNumber> >>> to no avail. Tried all available block numbers that are listed >>> when original mkfs was done, and it's output was saved. >>> >>> None of the blocks seem to work - all of them have invalid magic. >> >> Verify that the partition table st...

...nd tind blocks. For the answer, I want to summarize, how big files are stored. 4.1. The first 12 block numbers are stored in the inode itself. This is a good way to speed up access to small files. 4.2. The next 256 (512; 1024) block numbers are stored in a separate block, which's blocknumber will be stored as 13. block number in the inode. 4.3. The next 256^2 (512^2; 1024^2) block numbers are stored in 256 (512; 1024) separate blocks, which's block numbers are collected together in a double indirect block, which's block number is stored as 14. block numb...

Daniel, Ok, thanks. Simple fix. We'll just make correction in local copy for now, one less thing to port later :) Thanks. On Mon, Jul 27, 2015 at 12:29 PM, Daniel Sanders <Daniel.Sanders at imgtec.com> wrote: > I've just looked at my checkout of 3.6 and it looks like the fix wasn't > merged. I don't have the revision number for the fix to hand but in >

...t; >> On 09/18/2014 07:01 PM, Robert Nichols wrote: >>> On 09/18/2014 12:37 PM, jd1008 wrote: >>>> Is there any other tool that can extract files from a partition that >>>> seems to have corrupted superblocks? >>>> I tried dumpe2fs, and fsck -b <blockNumber> >>>> to no avail. Tried all available block numbers that are listed >>>> when original mkfs was done, and it's output was saved. >>>> >>>> None of the blocks seem to work - all of them have invalid magic. >>> Verify that the partition...

I have setup nut-2.4.1 with the bcmxcp driver for my HP R3000 XR unit and although it appears to work, I receive the following sorts of errors in syslog: Aug 27 10:33:05 sv18 bcmxcp[6373]: Communications with UPS lost: Receive error (data): got 0 bytes instead of 64!!! Aug 27 10:33:15 sv18 bcmxcp[6373]: Communications with UPS lost: Receive error (data): got 0 bytes instead of 64!!! Aug 27

Hi list this is actually a problem on a debian system but I thought you might be interested to hear of it and perhaps can offer some help. I have a woody box (dell pe750, dual cpu) running a kernel from backports.org (debian 'testing' packages built on a 'stable' box). The kernel version is 2.6.7-1.backports.org.1. This host is hooked up to an Apple Xserve RAID with a 2.3Tbyte