similar to: umount problem

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 22/02/15 14:19, Leon Fauster wrote: > Hi, > > on an EL5 XEN DOM0 system I have following volume > > $ df -h /srv Filesystem Size Used Avail Use% Mounted > on /dev/sdc1 917G 858G 60G 94% /srv > > that partition was used by virtual machines but they were all > halted. > > service

Hi, on an EL5 XEN DOM0 system I have following volume $ df -h /srv Filesystem Size Used Avail Use% Mounted on /dev/sdc1 917G 858G 60G 94% /srv that partition was used by virtual machines but they were all halted. service xendomains stop $ xm list Name ID Mem(MiB) VCPUs State Time(s) Domain-0

Hi! I'm using the ntfs-3g module for my portable USB hard drive on Centos 5.4. When I plug it into my centos box it mounts fine, but its owned by root and nobody but root has permission to write to it. I've been perusing the ntfs-3g and fuse man pages (and other docs) and they all seem to say that the default settings should be to allow RW access to everyone. but that isn't what

Signed-off-by: Pino Tsao <caoj.fnst@cn.fujitsu.com> --- daemon/btrfs.c | 40 +++++++++++++++++++++++++++++++++++++++ generator/actions.ml | 19 +++++++++++++++++++ tests/btrfs/test-btrfs-devices.sh | 8 ++++++++ 3 files changed, 67 insertions(+) diff --git a/daemon/btrfs.c b/daemon/btrfs.c index 39392f7..acc300d 100644 --- a/daemon/btrfs.c +++

在 2015年06月12日 17:12, Pino Toscano 写道: > On Friday 12 June 2015 10:58:34 Pino Tsao wrote: >> Hi, >> >> 在 2015年06月11日 17:43, Pino Toscano 写道: >>> Hi, >>> >>> On Wednesday 10 June 2015 17:54:18 Pino Tsao wrote: >>>> Signed-off-by: Pino Tsao <caoj.fnst@cn.fujitsu.com> >>>> --- >>>> daemon/btrfs.c

Hi, 在 2015年06月11日 17:43, Pino Toscano 写道: > Hi, > > On Wednesday 10 June 2015 17:54:18 Pino Tsao wrote: >> Signed-off-by: Pino Tsao <caoj.fnst@cn.fujitsu.com> >> --- >> daemon/btrfs.c | 40 +++++++++++++++++++++++++++++++++++++++ >> generator/actions.ml | 19 +++++++++++++++++++ >> tests/btrfs/test-btrfs-devices.sh |

alex lupu <alupu01 at gmail.com> writes: > On Tue, Mar 17, 2015 at 4:16 AM, Ferenc Wagner <wferi at niif.hu> wrote: > >> alex lupu via Syslinux <syslinux at zytor.com> writes: >> >>?>? Obviously it would work IF I moved the vmlinuz >>> and initramfs ?files from /dev/sdd2 to /dev/sdd1. >>> >>> I figured that would probably be

On 10/25/2015 11:12 AM, Barry Brimer wrote: > I 'just' noticed that at some point, my USB backup drive on my server >> is >> mounted as read-only and all of my background sync cron jobs have been >> failing. >> >> So I need to fix this without rebooting the server. >> How can I get this drive r/w? > Have you tried "mount -o remount,rw

On Tue, Mar 17, 2015 at 4:16 AM, Ferenc Wagner <wferi at niif.hu> wrote: > alex lupu via Syslinux <syslinux at zytor.com> writes: > > ?>? > Obviously it would work IF I moved the vmlinuz > > and initramfs ?files from /dev/sdd2 to /dev/sdd1. > > > > I figured that would probably be considered non-standard Arch > ? ...? > > The standard

I have my 640GB USB drive connected to a CentOS 5 server and using fdisk, it seems to show a partition of the correct size, /dev/sdd1, but after mounting, the drive shows only 244M size. Does the message received when running fdisk below mean I should reformat this drive, I can't seemed to figure out how to do that with fdisk. Can someone tell me how to reformat, if needed? The drive is empty,

alex lupu via Syslinux <syslinux at zytor.com> writes: > On Mon, Mar 16, 2015 at 1:41 PM, Ady via Syslinux <syslinux at zytor.com> > wrote: > >> So, your "root" can still be pointing to sdd2; as long as the >> "vmlinuz-linux" and "initramfs-linux.img" files are located in sdd1 >> directly under the "EFI" directory.

From: Jan Kara <jack at suse.cz> If we race with commit code setting i_transaction to NULL, we could possibly dereference it. Proper locking requires the journal pointer (to access journal->j_list_lock), which we don't have. So we have to change the prototype of the function so that filesystem passes us the journal pointer. Also add a more detailed comment about why the function

Hi, When I upgraded my cluster, df started returning some odd numbers for my legacy volumes. Newly created volumes after the upgrade, df works just fine. I have been researching since Monday and have not found any reference to this symptom. "vm-images" is the old legacy volume, "test" is the new one. [root at st-srv-03 ~]# (df -h|grep bricks;ssh st-srv-02 'df -h|grep

If we race with commit code setting i_transaction to NULL, we could possibly dereference it. Proper locking requires journal pointer (journal->j_list_lock) we don't have. So we have to change the prototype of the function so that filesystem passes us the journal pointer. Also add more detailed comment about why function does what it does how it should be used. Thanks to Dan Carpenter

Package: xen-hypervisor-4.4-amd64 Version: 4.4.1-9+deb8u4 Severity: grave Justification: renders package unusable Dear Maintainer, * What led up to the situation? Running Backup Exec or a copy command to NFS-Share causes the VM regurarly to freeze. First message on VM-Console: ---------------------------------------------------------------------------------------------------------------

On Mon, Mar 16, 2015 at 1:41 PM, Ady via Syslinux <syslinux at zytor.com> wrote: > Hmm... AFAIK, efibootmgr currently accepts slash and automatically > converts it into backslash. So for a current version of efibootmgr, a > path like: > /EFI/syslinux/syslinux.efi > (including the initial slash) should be OK as command-line argument. > ?Right?. I just used the

Hello, I wonder if has seen a problem of the sorts I am describing as at the moment it is driving me nuts. We have an array of LSI disks (Hardware Raid 5) which are attached to a Linux node. The Node has a LSI929 dual fibre channel card that has a channel attached to controller A and B of the array. So we have a list of devices under /proc/partitions mapping what we are expecting to see

Hi I have a Firewire connected Micronet 1.5TB RAID with a single large ext3 filesystem on one partition on a dual Xeon system. I am checking out from an extremely large cvs repository (don't ask) to this drive over the course of many days, and intermittently I get bad blocks and the filesystem goes read-only. This is not related to any power failure or anything similar. The RAID is currently

Hello, After another power loss (I am fortune, am I not?) I have the following situation : Label: none uuid: ac155851-0e31-4aed-9ba4-ee712506368a Total devices 3 FS bytes used 1.02TB devid 1 size 931.51GB used 70.00GB path /dev/sdd1 devid 3 size 1.79TB used 66.52GB path /dev/md2 devid 2 size 914.70GB used 914.50GB path /dev/sda4 btrfs device delete does not work on both md2 and

This version fixes three bugs in the 2nd patch of this series that caused kernel BUG when the system was under race. We weren't accounting with t_oustanding_credits correctly, and there were race conditions caused by the fact the I had overlooked the fact that __jbd2_log_wait_for_space() and jbd2_get_transaction() requires j_state_lock to be write locked. Theodore Ts'o (3): jbd2: Use