similar to: Samba does not report I/O error to the client

Displaying 20 results from an estimated 400 matches similar to: "Samba does not report I/O error to the client"

2018 Jan 02
0
Samba does not report I/O error to the client
On Wed, Dec 27, 2017 at 12:12:33AM +0100, Dmitry Katsubo via samba wrote: > Dear Samba community, > > I am facing the following problem. I have the following share in my > /etc/samba/smb.conf: > > [external] > comment = "External Hard Drive" > path = /mnt/external > read only = no > > Sometimes it happens that external hard drive fails. Kernel
2007 Jul 14
1
Kernel panic in ext3:dx_probe, help needed
This may or may not be ext3 related but I am trying to find any pointers which might help me. I got a number of HP Proliant DL380 g5 with a P400 controller and also two qla2400 cards. The OS is RedHat EL4 U5 x86_64. Every time during reboot these systems panic after the last umount and I believe before the cciss driver is getting unloaded. The last messages I am able to see are: md: stopping
2003 Jan 16
0
[PATCH] Using qstr in ext3_get_parent()
Hi In ext3_get_parent(), quick string (struct qstr) can do the job, in place of declaring a dentry on stack. Following patch does this and saves few bytes on kernel stack. Thanks, Maneesh namei.c | 69 ++++++++++++++++++++++++++++++---------------------------------- 1 files changed, 33 insertions(+), 36 deletions(-) diff -urN linux-2.5.58-base/fs/ext3/namei.c
2012 Jan 25
0
[3.2.1] kernel BUG at fs/btrfs/disk-io.c:2835!
I want to report a btrfs bug that happened this morning on kernel 3.2.1. I was copying a +5 GB file between two external usb harddisks, one formated with btrfs (the source) and the other with ext4 (the destination). In the meantime I decided to compile the 3.3-rc1 kernel with the output dir on the ext4 external harddisk. After some time I started to get many I/O errors coming from the ext4 drive
2008 Sep 28
1
USB external HDD error messages
Hi - relatively inexperienced user here. I installed CentOS 5.2 yesterday (http install via a mirror, worked brilliantly), as well as a new Seagate 1Tb USB external HDD (from the new Xtreme line), for backup/media storage. Using fdisk I put two primary partitions on the Seagate, /dev/sde1 and /dev/sde2 (roughly half the drive each). Then I used mkfs.ext3 on both to create ext3 filesystems
2017 Sep 28
1
upgrade to 3.12.1 from 3.10: df returns wrong numbers
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
2013 Aug 11
2
(un)mounting takes a long time
Hello! I''m using ArchLinux with kernel Linux horus 3.10.5-1-ARCH #1 SMP PREEMPT. Mounting and unmounting takes a long time: # time mount -v /mnt/Archiv mount: /dev/sde1 mounted on /mnt/Archiv. mount -v /mnt/Archiv 0,00s user 0,16s system 1% cpu 9,493 total # sync && time umount -v /mnt/Archiv umount: /mnt/Archiv (/dev/sdd1) unmounted umount -v /mnt/Archiv 0,00s user
2006 Aug 04
3
OCFS2 and ASM Question
Ok guys & gals here is the scenario: 1.) Host RHEL 4 U3 2.6.9-34.0.2.EL 2.) OCFS2 latest version 3.) Successfully formatted & mounted OCFS2 filesystems on 2 nodes /dev/sdb1 /u02/oradata/usdev/voting /dev/sdc1 /u02/oradata/usdev/data01 /dev/sdd1 /u02/oradata/usdev/data02 /dev/sde1 /u02/oradata/usdev/data03 4.) Downloaded & installed ASMLib 2.0 on both nodes 5.) Ran
2007 Nov 29
1
RAID, LVM, extra disks...
Hi, This is my current config: /dev/md0 -> 200 MB -> sda1 + sdd1 -> /boot /dev/md1 -> 36 GB -> sda2 + sdd2 -> form VolGroup00 with md2 /dev/md2 -> 18 GB -> sdb1 + sde1 -> form VolGroup00 with md1 sda,sdd -> 36 GB 10k SCSI HDDs sdb,sde -> 18 GB 10k SCSI HDDs I have added 2 36 GB 10K SCSI drives in it, they are detected as sdc and sdf. What should I do if I
2019 Jan 29
2
C7, mdadm issues
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 has >> a *second* bad drive. Actually, I'm starting to wonder about that >> particulare hot-swap bay. >> >> Anyway, mdadm --detail shows /dev/sdb1 remove. I've added /dev/sdi1... >> but see both /dev/sdh1 and
2011 Feb 01
1
Setting up persistent LUNs
Hello everyone, I am trying to setup persistent LUNs and having problems. I've been following instructions I found on the web and they refer to editing /etc/scsi_id.config file and adding options=-g line there. After doing so, I should be able to run scsi_id -g -s /dev/sd* and get proper results. I've modified file /etc/scsi_id.config appropriately: [root at psrwjmsafs1 etc]# grep
2011 Apr 09
16
wrong values in "df" and "btrfs filesystem df"
Hallo, linux-btrfs, First I create an array of 2 disks with mkfs.btrfs -d raid0 -m raid1 /dev/sdb1 /dev/sdd1 and mount it at /srv/MM. Then I fill it with about 1,6 TByte. And then I add /dev/sde1 via btrfs device add /dev/sde1 /srv/MM btrfs filesystem balance /srv/MM (it run about 20 hours) Then I work on it, copy some new files, delete some old files - all works well. Only df
2013 Aug 12
1
BTRFS corruptions counter
Hi, We decided to give BTRFS a try. We find it very flexible and generally fast. However last week we had a problem with a Marvell controller in AHCI and one BTRFS formatted hard drive. We isolated the problem by relocating the disk to an Intel contoller (SATA controller: Marvell Technology Group Ltd. 88SE9172 SATA 6Gb/s Controller (rev 11) had a lot of problems and I managed to overcome them by
2019 Jan 29
2
C7, mdadm issues
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 >>>> has a *second* bad drive. Actually, I'm starting to wonder about >>>> that particulare hot-swap bay. >>>>
2019 Jan 22
2
C7 and mdadm
A user's system had a hard drive failure over the weekend. Linux RAID 6. I identified the drive, brought the system down (8 drives, and I didn't know the s/n of the bad one. why it was there in the box, rather than where I started looking...) Brought it up, RAID not working. I finally found that I had to do an mdadm --stop /dev/md0, then I could do an assemble, then I could add the new
2019 Jan 30
4
C7, mdadm issues
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
2012 Aug 01
1
How to trigger automount of USB drives in Centos6
In brief: Is there is anyway to trigger the same automount mechanism, that X appears to use, on unmounted USB drives that are already connected? Background: I've got a C6 server with default desktop GUI installed for the sake of the onsite admin. There is a bash script I wrote that runs every night checking for specific folders on any drive and dumps data into it. To ensure fs integrity, I
2008 May 09
1
disk partitioning - I'm missing something simple, I think
Hi all, Excuse the question as I'm sure those more experienced will find it simple. I've a CentOS5.1 box with six physical drives, two of which are used for nightly rsync backups. Contents of /etc/mtab, /etc/fstab, df and a brief narrative follow: ====================================================== # cat ./fstab /dev/VolGroup00/LogVol00 / ext3 defaults
2019 Jan 30
2
C7, mdadm issues
Alessandro Baggi wrote: > Il 30/01/19 14:02, mark ha scritto: >> 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:
2008 Jan 03
1
Weird crash with CentOS 5.1
Dear all. I'm experiencing a weird crash with one of our desktop running CentOS 5.1 We have 5 machines identical, onle one has this problem. Right after it starts, it will kernel panic. Unfortunately, from the backtrace this is all I've managed to get : serial port isn't working. So it's a manual copy of what the screen show. [<c04721f3>] sync_buffer+0x0/0x33