[Samba] Samba NFS Fedora Core 2 and Software Raid -- Ext3 fs got corrupted???

[Andrew Bartlett]

On Sat, 2004-07-03 at 04:13, Terry Bowling wrote:
> I'm running:
> Fedora Core 2 (2.6.6.1-435)
> Samba 3.0.3-5
> 
> My shared (raid1 mirror) data directory is:
> /dev/md3  (hda6,hdc6)  mounted as Ext3  to /sites
> 
> This is shared to 300 users as an nfs mount point to their Digital Unix
> workstations as well as a Samba share to their W2k PC's.
> 
> My users just reported a bunch of read only error messages.  Turns out, it
> corrupted the file system.  It said it had no errors and when I did an "mdadm
> --details /dev/md3"  it said the raid devices were clean.  But the filesystem
> was read only even for root.  I finally gave up and rebooted and it said the
> filesystem was corrupted and I would have to run fsck manually.  Are there any
> issues where Samba has been know to corrupt a filesystem?

No.  It is not possible for Samba (as a userspace application) to be
responsible for filesystem corruption.  This is the responsibility of
the kernel. 

If you are seeing such corruption, then it is a kernel bug, and needs to
be fixed there.  

I am also unaware of any situation in which Samba can 'trigger' such
corruption, so I think you should look instead at the usual problems -
unclean shutdowns etc, and/or possible kernel bugs.

Were your filesystems mounted read-only, or just permissioned that way?

Andrew Bartlett
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://lists.samba.org/archive/samba/attachments/20040703/320056ee/attachment.bin