From: Pol <polmail@gmail.com>
To: xfs@oss.sgi.com
Subject: Please Help
Date: Fri, 07 May 2010 13:36:18 +0200 [thread overview]
Message-ID: <4BE3FB32.8030709@gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1613 bytes --]
Good morning.
I'm writing from Barcelona and English is not my born language, so I'd
like to apologize in advance for any possible mistakes in my text.
I'm a Windows user who has recently moved to Linux (Ubuntu 10.04), and I
have a serious problem regarding my Hard Drives' File System.
I have a desktop version of Ubuntu and I'm a complete regular user.
I have two physical drives in my system:
1. 36GB: EXT4 partition for /, another EXT4 for /home and a SWAP one.
2. 1TB (for data) drive.
I generate so much video and music data per month (AVI, MKV, MP3, WAV)
because of my job, and need to copy it to external hard drives to ensure
I don't lose any of it.
My question is about the FS to use in these data drives.
I currently have all of them in XFS fyle system. Every file I generate
is saved in my internal XFS drive, and whenever the hd is almost full I
copy the important files to External Hard Drives which are also
formatted as XFS.
My problem comes after reading a couple of posts from 2006 in some
forums on the web. They said that XFS is very unsecure when a power
failure happens and recommended EXT3 (EXT4 these days I guess). They
said that after a power failure it's very common to see data loss
(something that never happened to me in all my years using NTFS).
As far as I know XFS is much more secure than NTFS so I don't really
understand this issue. I assume these people were talking about systems
which need to be continously writing to the disk, but my knowledge about
this is very limited.
Did I chose the correct FS for my drives?
Thank you very much for your time.
[-- Attachment #1.2: Type: text/html, Size: 1931 bytes --]
[-- Attachment #2: Type: text/plain, Size: 121 bytes --]
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2010-05-07 11:34 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-07 11:36 Pol [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-11-12 9:02 Please Help Richard
2019-11-12 8:32 Richard
2019-11-12 8:15 Richard
2019-11-12 7:08 Richard
2012-01-15 23:25 Tai Bei
2012-01-15 23:25 Tai Bei
2012-01-15 21:40 Tai Bei
2009-02-11 14:59 constantine
2007-10-10 5:56 please help cyjoyp
2004-06-28 21:56 Please help Sam Loy
2004-06-28 22:13 ` Antony Stone
2004-06-28 22:18 ` Marek Dohojda
[not found] ` <16609.34789.711050.944527@saint.heaven.net>
2004-06-29 16:57 ` Sam Loy
2004-05-02 14:13 raven
2004-05-03 13:21 ` Jeff Moyer
[not found] <001c01c0b04b$7b39df80$4c0c5c8c@trd.iii.org.tw>
2001-03-19 18:21 ` guru
2001-03-19 18:38 ` nick
2001-03-19 18:56 ` Jonathan Lundell
2001-03-19 23:29 ` Dr. Kelsey Hudson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4BE3FB32.8030709@gmail.com \
--to=polmail@gmail.com \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.