search for: s_id

Dear R users, I have some trouble with the aggregate function. Here are my data > daf S_id AF_Class count... R_gc_percent S_length 5 8264497 1 30 0.48 35678 6 8264497 3 7 0.48 35678 8 8264554 1 31 0.51 38894 9 8264554 2 11 0.51 38894 10 8264554 3 1 0.51 38894 for...

...66f2 100644 --- a/fs/btrfs/disk-io.c +++ b/fs/btrfs/disk-io.c @@ -2254,9 +2254,9 @@ int open_ctree(struct super_block *sb, goto fail_sb_buffer; } - if (sectorsize < PAGE_SIZE) { - printk(KERN_WARNING "btrfs: Incompatible sector size " - "found on %s\n", sb->s_id); + if (sectorsize != PAGE_SIZE) { + printk(KERN_WARNING "btrfs: Incompatible sector size(%lu) " + "found on %s\n", (unsigned long)sectorsize, sb->s_id); goto fail_sb_buffer; } -- 1.6.5.2 -- To unsubscribe from this list: send the line "unsubscribe linu...

I have two datasets, big and small. s_date<-c(?2005-12-02?, ?2005-12-01?, ?2004-11-02?,?2002-10-05?,?2000-12-15?) s_id<-c(?a?,?a?,?b?,?c?,?d?) b_date<- c(?2005-12-31?, ?2005-12-31?, ?2004-12-31?,?2002-10-05?,?2001-10-31?,?1999-12-31?) b_id<-c(?a?,?b?,?c?,?d?,?e?,?c?) small<-data.frame(date_=as.Date(s_date),id=s_id) big<-data.frame(date_=as.Date(b_date),id=b_id) For each row in ?big?, I want to lo...

...if (num_bits != bits_cleared) { mlog(ML_ERROR, "Trying to clear %u bits at offset %u in group " "descriptor # %llu (device %s), needed to clear %u bits\n", num_bits, bit_off, (unsigned long long)le64_to_cpu(bg->bg_blkno), alloc_inode->i_sb->s_id, bits_cleared); } If this case happens, does it mean the filesystem have already been inconsistent? If so, why not set EROFS when this case happens? Or anyone knows which case will casue bits to be cleared multiple times? Thanks very much.

...g 2005-01-18 15:07:47.673128436 -0500 +++ linux-2.6.10/fs/ext3/super.c 2005-01-18 15:43:55.311501654 -0500 @@ -143,9 +143,6 @@ if (sb->s_flags & MS_RDONLY) return; - if (test_opt (sb, ERRORS_PANIC)) - panic ("EXT3-fs (device %s): panic forced after error\n", - sb->s_id); if (test_opt (sb, ERRORS_RO)) { printk (KERN_CRIT "Remounting filesystem read-only\n"); sb->s_flags |= MS_RDONLY; @@ -156,6 +153,9 @@ if (journal) journal_abort(journal, -EIO); } + if (test_opt (sb, ERRORS_PANIC)) + panic ("EXT3-fs (device %s): panic forced aft...

hello, Chris In the next several months, I will have a lot of spare time. I will be happy if you assign some work to me. I have learn linux kernel for years but only fix a few small bugs in IP stack. In the past few months, I read some EXT4/VFS codes. I began reading source of btrfs ten days ago and have read it twice now. Regards YZ

...uot;99.0" "117.0" "84.0" "33.0" [14,] "bp" "25155" "2012-02-06T13:48:42.042+05:30" "9830576102" "99.0" "117.0" "84.0" "33.0" > > colnames(matr)<-c("Type", "S_Id", "Record_time", "P_id", "Pulse_rate", "Syst", "Dias", "Pres") Note column names must be inserted before computing the desired mean value. matr1<-as.data.frame(matr) > matr1 Type S_Id...

...ret; + if ((ret = le32_to_cpu(EXT3_HAS_RO_COMPAT_FEATURE(sb, + ~EXT3_FEATURE_RO_COMPAT_SUPP)))) { printk(KERN_WARNING "EXT3-fs: %s: couldn't " "remount RDWR because of unsupported " "optional features (%x).\n", - sb->s_id, le32_to_cpu(ret)); + sb->s_id, ret); return -EROFS; } /* Index: linux-warnings/fs/ext3/resize.c =================================================================== --- linux-warnings/fs/ext3/resize.c (revision 14) +++ linux-warnings/fs/ext3/resize.c (revision 20) @@ -328,...

...and p, and h is essentially a sum over the volume at each p. When the individual models are computed, coefficients should be chosen so that this is satisfied. How to do this in R? Without the coupling the least-squares formulation would seek coefficients a_p and b_p to minimize: sum_p(sum_p((s_id,p - a_p t_id,p + b_k)^2)). Minimization at each p is independent. With coupling, there would be an additional term: sum_id((sum_p(vp)-h_id)^2) where vp is a function of a_p t_id,p + b_k and of t_id. The functions for vp are nonlinear, but if necessary with some work it should be possible to ge...

...handle; + struct super_block *sb = dquot->dq_sb; + struct ocfs2_mem_dqinfo *oinfo = sb_dqinfo(sb, type)->dqi_priv; + struct ocfs2_super *osb = OCFS2_SB(sb); + int status = 0; + + mlog_entry("id=%u qtype=%u type=%lu device=%s\n", dquot->dq_id, + dquot->dq_type, type, sb->s_id); + if (type != dquot->dq_type) + goto out; + status = ocfs2_inode_lock(oinfo->dqi_gqinode, &oinfo->dqi_gqi_bh, 1); + if (status < 0) + goto out; + + handle = ocfs2_start_trans(osb, OCFS2_QSYNC_CREDITS); + if (IS_ERR(handle)) { + status = PTR_ERR(handle); + mlog_errno(status); +...

Hi all - Here''s my current error handling patchset, against 3.1-rc8. Almost all of this patchset is preparing for actual error handling. Before we start in on that work, I''m trying to reduce the surface we need to worry about. It turns out that there is a ton of code that returns an error code but never actually reports an error. The patchset has grown to 65 patches. 46 of them

...ce the filesystem is unmounted.\n"); > > - if (osb->s_mount_opt & OCFS2_MOUNT_ERRORS_PANIC) > + if (osb->s_mount_opt & OCFS2_MOUNT_ERRORS_PANIC) { > panic("OCFS2: (device %s): panic forced after error\n", > sb->s_id); > + } else if (osb->s_mount_opt & OCFS2_MOUNT_ERRORS_CONT) { > + pr_crit("OCFS2: Returning error to the calling process.\n"); > + rv = -EIO; > + } else { /* default option */ > + rv = -EROFS; > + if (sb-&gt...

...ce the filesystem is unmounted.\n"); > > - if (osb->s_mount_opt & OCFS2_MOUNT_ERRORS_PANIC) > + if (osb->s_mount_opt & OCFS2_MOUNT_ERRORS_PANIC) { > panic("OCFS2: (device %s): panic forced after error\n", > sb->s_id); > + } else if (osb->s_mount_opt & OCFS2_MOUNT_ERRORS_CONT) { > + pr_crit("OCFS2: Returning error to the calling process.\n"); > + rv = -EIO; > + } else { /* default option */ > + rv = -EROFS; > + if (sb-&gt...

...* record an error on disk and force a filesystem check on the next boot. - */ -NORET_TYPE void ext3_panic (struct super_block * sb, const char * function, - const char * fmt, ...) -{ - va_list args; - - va_start(args, fmt); - printk(KERN_CRIT "EXT3-fs error (device %s): %s: ",sb->s_id, function); - vprintk(fmt, args); - printk("\n"); - va_end(args); - - /* this is to prevent panic from syncing this filesystem */ - /* AKPM: is this sufficient? */ - sb->s_flags |= MS_RDONLY; - panic ("EXT3-fs panic forced\n"); -} - void ext3_warning (struct super_block * sb...

I tried calling their toll free number and toll number last week in the morning and afternoon and was handed a recording saying this number is no longer in service. The web site was up but there was no message on the site as to why the phone numbers were not working. I just called the number now and it is working. Being around the internet for a quite a long time this gives me an uneasy

Hi all - The following 9 patches add more error handling to the btrfs code: - Add btrfs_panic - Catch locking failures in {set,clear}_extent_bit - Push up set_extent_bit errors to callers - Push up lock_extent errors to callers - Push up clear_extent_bit errors to callers - Push up unlock_extent errors to callers - Make pin_down_extent return void - Push up btrfs_pin_extent errors to

The biggest one is a fix for fstrim, and there''s a fix for on-disk free space cache. Others are small fixes and cleanups. The last three have been sent weeks ago. The patchset is also available in this repo: git://repo.or.cz/linux-btrfs-devel.git for-chris Note there''s a small confict with Al Viro''s vfs changes. Li Zefan (11): Btrfs: add pinned extents to

...ree(struct super_block *sb, goto fail_sb_buffer; } +#if 0 + // Hmm. How to deal wth this for subpagesize blocksize? if (sectorsize != PAGE_SIZE) { printk(KERN_WARNING "btrfs: Incompatible sector size(%lu) " "found on %s\n", (unsigned long)sectorsize, sb->s_id); goto fail_sb_buffer; } +#endif mutex_lock(&fs_info->chunk_mutex); ret = btrfs_read_sys_array(tree_root); diff --git a/fs/btrfs/extent_io.c b/fs/btrfs/extent_io.c index 1b319df..c1e052e 100644 --- a/fs/btrfs/extent_io.c +++ b/fs/btrfs/extent_io.c @@ -2519,7 +2519,7 @@ static int...

Hi, All the reviews for the AMD 890fx chipset reported that it supports IOMMU v1.2. But I cannot find any mention of that on AMD site. Does 890fx support IOMMU? Do 890fx motherboards with IOMMU exist? Does Xen support 890fx? Regards, Leonardo _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

ocfs2 currently uses the Journaled Block Device (JBD) for its journaling. This is a very stable and tested codebase. However, JBD is limited by architecture to 32bit block numbers. This means an ocfs2 filesystem is limited to 2^32 blocks. With a 4K blocksize, that's 16TB. People want larger volumes. Fortunately, there is now JBD2. JBD2 adds 64bit block number support and some other