similar to: Btrfs_truncate ?

I have a weird situation with a new installation of CentOS 5.4 x64, on a SuperMicro X7SBI server. The server has a <a href=" http://www.supermicro.com/products/motherboard/Xeon3000/3210/X7SBi.cfm" target="_new">SuperMicro X7SBi motherboard</a>, board ATI ES1000 and Core2Quad Q9505 CPU. The kernel is When I login to the console, using a "17 CRT monitor

On 03/27/2017 04:03 PM, Kevin Stange wrote: > On 03/25/2017 02:35 PM, Sarah Newman wrote: >> On 03/16/2017 04:22 PM, Kevin Stange wrote: >> >>>> I still can't rest assured the NIC issue is fixed, but no 4.4 or 4.9 >>>> server has yet had a NIC issue, with some being up almost a full month. >>>> It looks promising! (I'm knocking on all the

Greetings, Wondering if anyone could assist with this. I have many SuperMicro 5015B-MTB servers. These all have the X7SBi Motherboards. After upgrading to CentOS 5.3 the Hard Drive LED's on some of the servers started blinking red(drive fail) but all is functioning normally. All servers are running raid 1 arrays with MDADM. Primary drive does not blink, but all others do including spares.

Package: xen-hypervisor-3.2-1-amd64 Version: 3.2.1-2 Severity: normal *** Please type your report below this line *** Hi, Recently I've experienced some crashes of Xen domU (also debian Lenny, running same kernel as dom0 (linux-image-2.6.26-xen-amd64)). At xm top that domain appears as running, but hogs all CPUs, because this problem has appeared on two identic servers (Supermicro X7SBi,

The original truncation of btrfs has a bug, that is the orphan item will not be dropped when the truncation fails. This bug will trigger BUG() when unlink that truncated file. And besides that, if the user does pre-allocation for the file which is truncated unsuccessfully, after re-mount(umount-mount, not -o remount), the pre-allocated extent will be dropped. This patch modified the relative

Hi All, I would be lying if I said I am a newbie, but I am rusty so please bear with me. I am looking for a how-to for Redhat or Centos to remake the installation CD. First let me explain: I have an installation disc supplied to me, with centos 5.2 which has kickstart, post and pre installation scripts which run. The problem we have is that the CD does not support our CDROM (it8213). I have

When btrfs_start_transaction() fails, we should call btrfs_std_error() properly for filesystem to readonly. (in this patch, forced readonly framework is used) Signed-off-by: Tsutomu Itoh <t-itoh@jp.fujitsu.com> --- fs/btrfs/file.c | 1 + fs/btrfs/inode.c | 34 +++++++++++++++++++++++++++------- fs/btrfs/ioctl.c | 11 ++++++++++- fs/btrfs/relocation.c | 4 +++-

I converted btrfs_truncate to do sane reservations for truncate, but didn''t convert btrfs_evict_inode. Basically we need to save the orphan_rsv for deleting the orphan item, and do normal reservations for our truncate. Thanks, Signed-off-by: Josef Bacik <josef@redhat.com> --- fs/btrfs/inode.c | 31 +++++++++++++++++++------------ 1 files changed, 19 insertions(+), 12

I noticed we were getting lots of warnings with xfstest 83 because we have reservations outstanding. This is because we moved the orphan add outside of the truncate, but we don''t actually cleanup our reservation if something fails. This fixes the problem and I no longer see warnings. Thanks, Signed-off-by: Josef Bacik <jbacik@fusionio.com> --- fs/btrfs/inode.c | 2 ++ 1

I have a raidz2 and did a scrub, it took 8h. Then I reconnected some drives to other SATA ports, and now it takes 15h to scrub?? Why is that? -- This message posted from opensolaris.org

After running ceph on XFS for some time, I decided to try btrfs again. Performance with the current "for-linux-min" branch and big metadata is much better. The only problem (?) I''m still seeing is a warning that seems to occur from time to time: [87703.784552] ------------[ cut here ]------------ [87703.789759] WARNING: at fs/btrfs/inode.c:2103

On 03/16/2017 04:22 PM, Kevin Stange wrote: >> I still can't rest assured the NIC issue is fixed, but no 4.4 or 4.9 >> server has yet had a NIC issue, with some being up almost a full month. >> It looks promising! (I'm knocking on all the wood everywhere, though.) > > I'm ready to call this conclusive. The problems I was having across the > board seemed to

If we have particularly full nodes, we could call btrfs_node_blockptr up to 32 times, which is 32 pairs of kmap/kunmap, which _sucks_. So go ahead and map the extent buffer while we look for readahead targets. Thanks, Signed-off-by: Josef Bacik <josef@redhat.com> --- fs/btrfs/ctree.c | 23 +++++++++++++++++++++-- 1 files changed, 21 insertions(+), 2 deletions(-) diff --git

Group, My linux box, running with Centos-5.5, is showing up (??) a pseudo network interface for Eth0. On Switch where my Eth0 is connected, observed 2 MAC-Addresses. If a DHCP server present in LAN, the second pseudo interface is picking up a DHCP IP Address too. Furthermore you can ping both Eth0 ip and Psedo Eth0 IP from the switch. The intensity of the problem is more when port-security is

I noticed that if the free space cache has an error writing out it''s data it won''t actually error out, it will just carry on. This is because it doesn''t check the return value of btrfs_wait_ordered_range, which didn''t actually return anything. So fix this in order to keep us from making free space cache look valid when it really isnt. Thanks, Signed-off-by:

Hello, I''m seeing a lot of warnings in dmesg with a BTRFS filesystem. I''m using the 3.1 kernel, I found a patch for these warnings ( http://marc.info/?l=linux-btrfs&m=131547325515336&w=2) <http://marc.info/?l=linux-btrfs&m=131547325515336&w=2>, but that patch has already been included in 3.1. Are there any other patches I can try? I''m using

Hi, I am trying to use sub, regexpr on expressions like log(D) ~ log(N)+I(log(N)^2)+log(t) being a model specification. The aim is to produce: "ln D ~ ln N + ln^2 N + ln t" The variable names N, t may change, the number of terms too. I succeded only partially, help on regular expressions is hard to understand for me, examples on my case are rare. The help page on R-help

This patch finally gives us full proper -ENOSPC handling for btrfs. Now whenever you do a btrfs_start_transaction, you must specify the number of items you are planning to add/delete/modify. The worst case number of blocks that could be modified by changing that number of items will be calculated and checked against the amount of free space in the space_info where the root you are modifying

Document those places in the btrfs code which are BUGing on non-fatal error conditions that should be handled by proper error paths. This makes it easier to distinguish between what needs fixing versus which BUG_ON''s we might want to keep (to trap code bugs, unexpected inconsistencies, etc). Do this with a trivial macro, ''btrfs_fixable_bug_on'' which just defines to

When adding orphans to an inode''s root, we start a transaction for that root that when ended in several places such as for example extent-tree.c:btrfs_remove_block_group(), inode.c:btrfs_unlink() and inode.c:btrfs_evict_node(), doesn''t result in a commit, that is, inode.c:btrfs_orphan_commit_root() doesn''t get called (via transaction.c:commit_fs_roots()). The respective