Pantek Library
Hosting Provided By
CybrHost
High Speed Hosting
Mailing Lists: lists.debian.org > debian-user-digest > 07 > 080268.html (Request Expert lists.debian.org Support)

debian-user-digest Digest V2007 #2095

From: <debian-user-digest-request(at)lists.debian.org>
Date: Sat Aug 04 2007 - 02:06:13 EDT


Content-Type: text/plain

debian-user-digest Digest Volume 2007 : Issue 2095

Today's Topics: 

  Re: ntfs mount errors                 [ Phill Atwood  ]
  Re: ntfs mount errors                 [ Andrew Sackville-West  ]
  Re: Opinions XFS                      [ bob@proulx.com (Bob Proulx) ]
  Re: Opinions XFS                      [ bob@proulx.com (Bob Proulx) ]
  Re: Opinions XFS                      [ Josh Hansen 

Date: Fri, 03 Aug 2007 23:17:21 -0400


From: Phill Atwood <me@phillatwood.name>
To: Stephan Hachinger <stephan.hachinger@gmx.de>
Cc: debian-user@lists.debian.org


Subject: Re: ntfs mount errors

Message-Id: <1186197441.3961.28.camel@goonyam.goonyam.local>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit


On Sat, 2007-04-08 at 01:24 +0200, Stephan Hachinger wrote:

> Hi Phil,
> 
> err ... well, which suggestion? Anyway, I found the following:
> 

Maybe it was Doug who made the suggestion.


> * Are you using "alternative data streams" [sorry, that's an direct German to English translation ... don't know how this is called on English windoze], compressed or encrypted files? If so, this could cause problems.
> 
> * Are you using a "dynamical volume" [direct translation again, seems to be some kind of extendible partitions - I've never used that windoze feature]?
> 
> * If all the things above do not apply, try marking the fs as dirty, rebooting (chkdsk checks), then rebooting a second time into windoze, then rebooting into linux (see http://lists.debian.org/debian-user/2006/03/msg03215.html)
> 
> As for the umask, I don't know exactly what you've done, but the following posting might be interesting: http://osdir.com/ml/linux.file-systems.ntfs.user/2006-05/msg00004.html . "umask=0222" seems to be a quick and dirty way to make it accessible to any user. For the long term however, maybe you can try to figure out a good and clean way to do it, with these groups etc.
> 
Do you need help?X

Success.  Although I can't say that I really understand. Setting
umask=0222 in the /etc/fstab file did the trick.  I don't understand why
mounting a ro partition to a directory with just write permissions would
work. 0544 or 0555 seemed the more logical thing to try...



As a relative newby here are some things I noted that I don't get. 



  1.   Previously, I made a group and added my users to it, editted fstab to
allow gid for that group, chmoded the directory to 0544 and set the
umask in fstab to be 0544 too.  This almost worked.  I was able to cd to
my windoze directory, but I couldn ls -l it!  

  
  2.   When I created my new group bar and added my user foo to it with
"adduser foo bar" it worked.  When I issued the "groups" command it did
not show bar as being one of the groups that foo belonged to.  I
rebooted, issued "groups" again and now foo is in bar.  Seems to me it
should know this right away without a reboot...  (I'm showing my Windoze
ancestry by rebooting all the time!)

  
  3.   Even after this success, dmesg shows:




NTFS volume version 3.1.


NTFS-fs warning (device sda1): load_system_files(): Unsupported volume
flags 0x4000 encountered.


NTFS-fs error (device sda1): load_system_files(): Volume has unsupported
flags set.  Mounting read-only.  Run chkdsk and mount in Windows.



I did go into windoze and run chkdsk after forcing the dirty bit.  It
found no errors.  But I still get the msg on the linux side.



I've probably got my head in the clouds, but is any of this a bug in
Debian.  Especially a) and b).  I'll have to figure out the BTS system
to find out...


> Another thing: If you also need write access onto ntfs, and want read access onto compressed files, then the ntfs-3g driver might be interesting for you. For newbies however, it might not be that easy to install... you need to make a package for stable yourself. On the other hand, if you'd need it, I can just do an update/recompile here on my system and send the resulting package to you via email.
> 
> Cheers,
> 
> Stephan
> 

I had run into ntfs-3g while googling earlier.  It does intrigue me.
Making my own package to install it is probably way over my head.
Although, I would like to get into package maintenance.  If this is not
too big a piece to chew on I would be willing to take whatever time to
try.  I am sceptical that previous versions of Debian don't trust ntfs
to write but these ntfs-3g guys do.  I also read that if you mount
windows xp as vfat you can write to it.  Even more sceptical.



If you are willing to recompile it for me I'd try it.  I can't afford to
loose that data, so I would back it up first.


Do you need more help?X

Thanks for your help Stephan.  Doug and others too.  This beats windoze
help/obfuscation hands down!



Phill




> 
> On Fri, 03 Aug 2007 12:30:50 -0400
> Phill Atwood <me@phillatwood.name> wrote:
> 
> > 
> > Stephan,
> > 
> > Thanks for your suggestion.  It was a good one that I had overlooked
> > despite having read the mount man page.  However, I tried it and it
> > didn't work.  At least I tried using a umask.  I still should try
> > setting up a group and setting the gid.
> > 
> > I still get the error messages in dmesg, as follows:
> > 
> > NTFS driver 2.1.27 [Flags: R/W MODULE].
> > NTFS volume version 3.1.
> > NTFS-fs warning (device sda1): load_system_files(): Unsupported volume
> > flags 0x4000 encountered.
> > NTFS-fs error (device sda1): load_system_files(): Volume has unsupported
> > flags set.  Mounting read-only.  Run chkdsk and mount in Windows.
> > 
> > It is not a high priority issue.  It's just bugging me.  I hope to look
> > into it more tonight or tomorrow.
> > 
> > Your help has been appreciated.
> > 
> > Phill
> > 
> > 
> > On Fri, 2007-03-08 at 12:56 +0200, Stephan Hachinger wrote:
> > > Douglas Allan Tutty <dtutty@porchlight.ca> wrote:
> > > 
> > > > On Wed, Aug 01, 2007 at 04:49:04AM +0200, pinniped wrote:
> > > > > 
> > > > > (quote)
> > > > > I still have the problem. ie. The windoze partition is
> > > > > mounted automatically fine, but I can only cd to it if I am root.
> > > > > (end quote)
> > > > > 
> > > > > Do:
> > > > > man mount
> > > > > 
> > > > > Look at the 'Mount options for ntfs'. All your mysteries are explained 
> > > (...)
> > > > > So you need to set the uid/gid and umask. You really want 'root' to be the 
> > > > > owner anyway so I guess you only want to change the gid to the 'disk' group 
> > > > > and make sure you have a sensible umask.
> > > > 
> > > > Be careful there, members of the 'disk' group can do nasty things on
> > > > your debian box too.  Perhaps create a new group who can access the
> > > > windows partition, put those users into the group, then use the gid=
> > > > parameter in fstab.  However, this doesn't affect the uid.  I can't test
> > > (...)
> > > 
> > > Hi Phill,
> > > 
> > > short "PM": Does this work now? And: Has the error msg in dmesg gone away?
> > > 
> > > 
> > > Cheers,
> > > 
> > > Stephan

Date: Fri, 3 Aug 2007 20:51:50 -0700


From: Andrew Sackville-West <andrew@farwestbilliards.com>
To: debian-user@lists.debian.org


Subject: Re: ntfs mount errors


Message-ID: <20070804035150.GH31947@localhost.localdomain>
Content-Type: multipart/signed; micalg=pgp-sha1;


        protocol="application/pgp-signature"; boundary="Q6STzHxy03qt/hK9"
Content-Disposition: inline



--Q6STzHxy03qt/hK9

Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable


On Fri, Aug 03, 2007 at 11:17:21PM -0400, Phill Atwood wrote:

>=20
>=20
>=20


> Success.  Although I can't say that I really understand. Setting
> umask=3D0222 in the /etc/fstab file did the trick.  I don't understand why
> mounting a ro partition to a directory with just write permissions would
> work. 0544 or 0555 seemed the more logical thing to try...
Can we help you?X

its a mask so you turn on the bits you want off in the final result.



if one digit of your mask is 2 then it looks like:  010
that makes the final perm is 5 and it looks like:   101



if the mask is 0 :   000


then perm is 7 or :  111


so a mask of 5:	     101
becomes perm 2:	     010


and not what you want.=20



So I'm not sure how that translates to the first digit since i'm sure
you don't want a perm to come out 7555 using umask of 0222 but maybe
someone can enlighten


>=20


> As a relative newby here are some things I noted that I don't get.=20
>=20


> a) Previously, I made a group and added my users to it, editted fstab to
> allow gid for that group, chmoded the directory to 0544 and set the
> umask in fstab to be 0544 too.  This almost worked.  I was able to cd to
> my windoze directory, but I couldn ls -l it! =20

I don't remember how it works. 0544 gives you perms of 0255 or
-w-r-xr-x so the owner can't ls it as you can neither read nor
execute, but I'm surprised you could cd to it  too... its confusing, i
know.


>=20


> b) When I created my new group bar and added my user foo to it with
> "adduser foo bar" it worked.  When I issued the "groups" command it did
> not show bar as being one of the groups that foo belonged to.  I
> rebooted, issued "groups" again and now foo is in bar.  Seems to me it
> should know this right away without a reboot...  (I'm showing my Windoze
> ancestry by rebooting all the time!)

you get your groups at login. Until you log out and log back in, you
won't get new groups. You don't need to reboot, just log out
everywhere and log back in.=20


>=20


> c) Even after this success, dmesg shows:
>=20


> NTFS volume version 3.1.
> NTFS-fs warning (device sda1): load_system_files(): Unsupported volume
> flags 0x4000 encountered.
> NTFS-fs error (device sda1): load_system_files(): Volume has unsupported
> flags set.  Mounting read-only.  Run chkdsk and mount in Windows.

i see that a lot and never have any problems. FWIW. but avoid writing
in ntfs if you can.


Can't find what you're looking for?X

=2E..


> > Another thing: If you also need write access onto ntfs, and want read a=
ccess onto compressed files, then the ntfs-3g driver might be interesting f=
or you. For newbies however, it might not be that easy to install... you ne=
ed to make a package for stable yourself. On the other hand, if you'd need =
it, I can just do an update/recompile here on my system and send the result=

Don't know where to look next?X



ing package to you via email.



is it in backports?



A



--Q6STzHxy03qt/hK9

Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----


Version: GnuPG v1.4.6 (GNU/Linux)



iD8DBQFGs/fWaIeIEqwil4YRAja/AJ9APAknSIDmziOkD91U5bwnKjLozACdH2Pl
+HcZ+1rlkQMYlqPVyUpnsv4=


=hCuY

-----END PGP SIGNATURE-----


--Q6STzHxy03qt/hK9--


Confused? Frustrated?X

Date: Sat, 4 Aug 2007 00:37:38 -0300


From: Sergio Belkin <sebelk@gmail.com>


To: debian-user@lists.debian.org


Subject: Re: Opinions XFS


Message-Id: <200708040037.39078.sebelk@gmail.com>
Content-Type: text/plain;


  charset="iso-8859-1"


Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline



=2D-- El Vie 03 Ago 2007, michael@estone.ca encontr=F3 un teclado y tipe=F3=
 lo=20


siguiente:=20

> mi: XFS and grub do not work nicely together, therefore you'll need /boot=

 =A0

> mi: mounted with EXT3, everything else can be XFS, even / .
> mi:

And What about lilo?



=2D-=20


Sergio Belkin


Tel=E9fonos 15-5494-5143 //  4788-8605

=2D---------------------------------------


Date: Fri, 3 Aug 2007 21:55:39 -0600


From: bob@proulx.com (Bob Proulx)


To: debian-user@lists.debian.org


Subject: Re: Opinions XFS

Message-ID: <20070804035539.GA25575@dementia.proulx.com>
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline


Sergio Belkin wrote:

> Hi I was reading http://oss.sgi.com/projects/xfs/index.html and was amazed 
> because XFS powerful features. But I'd like opinions if xfs should be a good 
> alternative to ext3 in typical cases, or if it should be relegated to 
> critical missions servers.

I like and have used XFS.  But it is lacking one feature that is
important to me and that is the ability to shrink the filesystem.
Both ext2 and ext3 filesystems can be resized up or down with
resize2fs.  That allows me to rebalance disk space and useful in
conjunction with LVM.  With the xfs filesystem xfs_growfs can be used
to grow it but not to shrink it.  Because xfs can't shrink this limits
the ability to rebalance disk space.


Call Pantek today for Open Source Technical Support at 1-877-546-8934 - 24/7/365X

Bob



Date: Fri, 3 Aug 2007 22:00:32 -0600


From: bob@proulx.com (Bob Proulx)


To: debian-user@lists.debian.org


Subject: Re: Opinions XFS

Message-ID: <20070804040032.GB25575@dementia.proulx.com>
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable


Sergio Belkin wrote:

> --- El Vie 03 Ago 2007, michael@estone.ca encontr=F3 un teclado y tipe=F3=

 lo=20

> siguiente:=20
> > mi: XFS and grub do not work nicely together, therefore you'll need /=

boot =A0

> > mi: mounted with EXT3, everything else can be XFS, even / .
> > mi:


>=20

> And What about lilo?

I would not even worry about trying to put /boot on xfs, jfs,
reiserfs, or any other journaling filesystems.  I don't even use ext3
for it because the journal takes up such a large amount of space it
can be a problem.  Even when using a large /boot of say 512MB this is
tiny and journaling is not needed.  Also /boot cannot be on an LVM
partition.  I always use a large 512MB ext2 /boot partition.



Bob



Date: Fri, 03 Aug 2007 22:04:05 -0600


From: Josh Hansen <josh_lists@xmission.com>
To: Sergio Belkin <sebelk@gmail.com>


Cc: debian-user@lists.debian.org


Subject: Re: Opinions XFS

Message-ID: <46B3FAB5.9080309@xmission.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Do you need help?X

Sergio Belkin wrote:

> --- El Vie 03 Ago 2007, michael@estone.ca encontr=F3 un teclado y tipe=F3=

 lo=20

> siguiente:=20


>> mi: XFS and grub do not work nicely together, therefore you'll need /b=
oot =20

>> mi: mounted with EXT3, everything else can be XFS, even / .
>> mi:
>=20


> And What about lilo?


>=20



lilo works fine with XFS.  grub actually does work with XFS as well, but
it has problems if you try to use grub-install to install it to XFS, or
from the debian installer.  Installing it the manual way from the grub
command line works perfectly.



Date: Sat, 4 Aug 2007 07:37:35 +0300


From: Andrei Popescu <andreimpopescu@gmail.com>
To: debian-user@lists.debian.org


Subject: Re: ntfs mount errors


Message-ID: <20070804043735.GC3810@think.homenet>
Content-Type: multipart/signed; micalg=pgp-sha1;


        protocol="application/pgp-signature"; boundary="/Uq4LBwYP4y1W6pO"
Content-Disposition: inline



--/Uq4LBwYP4y1W6pO

Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable


On Fri, Aug 03, 2007 at 11:17:21PM -0400, Phill Atwood wrote:
=20

> I had run into ntfs-3g while googling earlier.  It does intrigue me.
> Making my own package to install it is probably way over my head.
> Although, I would like to get into package maintenance.  If this is not
> too big a piece to chew on I would be willing to take whatever time to
> try.  I am sceptical that previous versions of Debian don't trust ntfs
> to write but these ntfs-3g guys do.=20

AFAIU ntfs-3g is a total rewrite of the (old) kernel ntfs driver. And=20
the guys seem pretty serious to me:


Do you need more help?X
http://www.ntfs-3g.org/quality.html

>I also read that if you mount

> windows xp as vfat you can write to it.  Even more sceptical.

What do you mean by that? You can safely mount fat partitions for a long=20
time now.



Regards,


Andrei


--=20


If you can't explain it simply, you don't understand it well enough.
(Albert Einstein)



--/Uq4LBwYP4y1W6pO

Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----


Version: GnuPG v1.4.6 (GNU/Linux)



iD8DBQFGtAKPqJyztHCFm9kRAu1iAJ4klLe5NLuVi6FZJYAxcqKg2YjlYgCfYNiH
cWRuyfLNEOLUj2SCIzUYM6E=


=S+39

-----END PGP SIGNATURE-----


--/Uq4LBwYP4y1W6pO--


Can we help you?X

Date: Sat, 4 Aug 2007 07:42:57 +0300


From: Andrei Popescu <andreimpopescu@gmail.com>
To: debian-user@lists.debian.org


Subject: Re: converting file system


Message-ID: <20070804044257.GD3810@think.homenet>
Content-Type: multipart/signed; micalg=pgp-sha1;


        protocol="application/pgp-signature"; boundary="fXStkuK2IQBfcDe+"
Content-Disposition: inline



--fXStkuK2IQBfcDe+

Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable


On Fri, Aug 03, 2007 at 08:23:17PM -0400, Douglas Allan Tutty wrote:
=20

> This is a great reason to be using LVM with separate LVs.  Need to
> convert?  Create a new LV, make the new filesystem, tar the data over to
> it.  When everything is working, delete the old LV.  If you need extra
> space during the transition, borrow a drive and add it to the VG.

=20


What's the benefit of LVM when I add a separate drive?



Regards,


Andrei


--=20


If you can't explain it simply, you don't understand it well enough.
(Albert Einstein)



--fXStkuK2IQBfcDe+

Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----


Version: GnuPG v1.4.6 (GNU/Linux)



iD8DBQFGtAPRqJyztHCFm9kRAutMAJ4599PHX69JuBiyLWZPHSemqfSqWQCgpmPg
ivOjRLRjSHp9VihG37h8qno=


=XqId

-----END PGP SIGNATURE-----


--fXStkuK2IQBfcDe+--


Can't find what you're looking for?X

Date: Sat, 4 Aug 2007 07:48:29 +0300


From: Andrei Popescu <andreimpopescu@gmail.com>
To: debian-user@lists.debian.org


Subject: Re: ext3fs errors with kernel 2.6.18 but not with 2.4.27
Message-ID: <20070804044829.GE3810@think.homenet>
Content-Type: multipart/signed; micalg=pgp-sha1;


        protocol="application/pgp-signature"; boundary="Oiv9uiLrevHtW1RS"
Content-Disposition: inline



--Oiv9uiLrevHtW1RS

Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable


On Sat, Aug 04, 2007 at 12:35:54AM -0400, Francois Duranleau wrote:
=20

> I tried to change the IDE cables (I had a few spares from my father's com=

puter).

> I happened to notice that I had a 40 pins cable. I replaced it with a 80 =

pins

> cable. I have two, I tried both: nothing changed. I still have CRC errors=
=2E BTW,

> there is only one drive on that cable.

>=20

> However, I noticed that the motherboard's chipset's fan is dead. I knew i=

t was

> having a hard time spinning lately, but now, it's gone. Would it be the
> motherboard's chipset that causes those errors because it's too hot?

Looks like a good candidate to me ...


> Well, once in a while, the kernel resets ide0, and then DMA is dropped (a=

nd I

> force it back on afterwards), which I guess is not a good idea.

Such troubles need to be investigated (says me who lost a disk without=20
any decent backups. At least no (very) important data on it).


Don't know where to look next?X

Regards,


Andrei


--=20


If you can't explain it simply, you don't understand it well enough.
(Albert Einstein)



--Oiv9uiLrevHtW1RS

Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----


Version: GnuPG v1.4.6 (GNU/Linux)



iD8DBQFGtAUcqJyztHCFm9kRAgMLAJ90QboeA2JGn2TydBNyxxlEyL4v8wCfVPaN
oVy9mRDzzMfP0hwl4vzpiEw=


=onF3

-----END PGP SIGNATURE-----


--Oiv9uiLrevHtW1RS--



Date: Sat, 4 Aug 2007 07:50:43 +0300


From: Andrei Popescu <andreimpopescu@gmail.com>
To: debian-user@lists.debian.org


Subject: Re: Blurry fonts in OpenOffice and qt4 appliations
Message-ID: <20070804045043.GF3810@think.homenet>
Content-Type: multipart/signed; micalg=pgp-sha1;


        protocol="application/pgp-signature"; boundary="R6sEYoIZpp9JErk7"
Content-Disposition: inline



--R6sEYoIZpp9JErk7

Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Confused? Frustrated?X

On Fri, Aug 03, 2007 at 07:15:39PM -0700, Alan Ianson wrote:

> On Fri August 3 2007 12:48, Vasil Benov wrote:
> > Hi all,
> >
> > The fonts in OpenOffice and qt4(skype 1.4 beta) applications are blurry.
> > Has anyone encountered the same problem?
> > There is a thread on the Ubuntu mailing list, but it does not offer any
> > solution.


>=20

> I noticed that too a while ago, one of the fonts I was using (sorry, I fo=

rget=20

> which one) seemed to have a rainbow color effect to it for reasons unknow=

n. I=20

> changed the system font to something else and it has looked fine since.

LCD or CRT monitor? Have a look at the sub-pixel rendering option=20
(dpkg-reconfigure fontconfig-config).



Regards,


Andrei


--=20


If you can't explain it simply, you don't understand it well enough.
(Albert Einstein)



--R6sEYoIZpp9JErk7

Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----


Version: GnuPG v1.4.6 (GNU/Linux)



iD8DBQFGtAWjqJyztHCFm9kRAu4uAJ9U0yup+9/RJFubCN8zfQiTVgRhMgCeLYod
RRHTJ4H8YoP3wXWFTEpet7Q=


=+R6x

-----END PGP SIGNATURE-----


--R6sEYoIZpp9JErk7--



Date: Sat, 4 Aug 2007 00:35:54 -0400


From: "Francois Duranleau" <xiao.bai.xiong@gmail.com>
To: debian-user@lists.debian.org


Subject: Re: ext3fs errors with kernel 2.6.18 but not with 2.4.27

Message-ID: <8eb883950708032135v6e8d8860lc525db58a7e930d8@mail.gmail.com>

Do you need help?X

Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Call Pantek today for Open Source Technical Support at 1-877-546-8934 - 24/7/365X

On 8/3/07, Brad Sawatzky <brad+debian@swatter.net> wrote:

> Hi Francois,
>


> I agree with Doug:  CRC errors shouldn't be ignored.  At _best_ they are a
> sign that something in your system is marginal.  At worst you end up
> reading and/or writing bogus data.  The fact that the errors persisted
> after you changed hard drives suggest either a bad cable (most likely), bad
> secondary device on that cable, or bad motherboard (unlikely).

I tried to change the IDE cables (I had a few spares from my father's computer).
I happened to notice that I had a 40 pins cable. I replaced it with a 80 pins
cable. I have two, I tried both: nothing changed. I still have CRC errors. BTW,
there is only one drive on that cable.



However, I noticed that the motherboard's chipset's fan is dead. I knew it was
having a hard time spinning lately, but now, it's gone. Would it be the
motherboard's chipset that causes those errors because it's too hot?


> > I will try to see tonight or tomorrow if I can manage to get some logs as
> > Douglas suggested. I will also try to look at what driver is in use also.
> > Looking at my config-2.6.18 file:
> >
> > http://www-etud.iro.umontreal.ca/~duranlef/linux-config/config-2.6.18
> >
> > it's hard to guess. All I know is that all SATA support is disabled.
>


> Your config file says that you're using the 'old' (stable) IDE driver, not
> the newer PATA drivers.  That's (probably) good.
>


> FWIW, you could try booting with the kernel option 'hda=autotune" or
> "idea=autotune" and see what happens.  That should allow the driver/chipset
> to fall back to a slower PIO mode if it sees CRC errors.  (Though I don't
> know what, if anything, it will do if DMA is enabled...)

Well, once in a while, the kernel resets ide0, and then DMA is dropped (and I
force it back on afterwards), which I guess is not a good idea.


-- 
Francois


Date: Fri, 3 Aug 2007 22:04:40 -0700
From: Andrew Sackville-West <andrew@farwestbilliards.com>
To: debian-user@lists.debian.org
Subject: Re: converting file system
Message-ID: <20070804050440.GI31947@localhost.localdomain>
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="7SrMUQONj8Rl9QNG"
Content-Disposition: inline

--7SrMUQONj8Rl9QNG
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Sat, Aug 04, 2007 at 07:42:57AM +0300, Andrei Popescu wrote:

> On Fri, Aug 03, 2007 at 08:23:17PM -0400, Douglas Allan Tutty wrote:
> =20
> > This is a great reason to be using LVM with separate LVs.  Need to
> > convert?  Create a new LV, make the new filesystem, tar the data over to
> > it.  When everything is working, delete the old LV.  If you need extra
> > space during the transition, borrow a drive and add it to the VG.
> =20
> What's the benefit of LVM when I add a separate drive?



you can add the drive to the VG and then create more LV's to shuffle
filesystems around to make the conversion possible.

A

--7SrMUQONj8Rl9QNG
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFGtAjoaIeIEqwil4YRAjgTAKDhast41vJxaJqEVMMccFzRoibAGgCggzVF
VlK7MiiYKZk0jcjdWu25pEE=
=wyqV
-----END PGP SIGNATURE-----

--7SrMUQONj8Rl9QNG--



Date: Sat, 4 Aug 2007 08:18:53 +0300
From: Andrei Popescu <andreimpopescu@gmail.com>
To: debian-user@lists.debian.org
Subject: Re: converting file system
Message-ID: <20070804051853.GG3810@think.homenet>
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="RDS4xtyBfx+7DiaI"
Content-Disposition: inline

--RDS4xtyBfx+7DiaI
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Fri, Aug 03, 2007 at 10:04:40PM -0700, Andrew Sackville-West wrote:

> On Sat, Aug 04, 2007 at 07:42:57AM +0300, Andrei Popescu wrote:
> > On Fri, Aug 03, 2007 at 08:23:17PM -0400, Douglas Allan Tutty wrote:
> > =20
> > > This is a great reason to be using LVM with separate LVs.  Need to
> > > convert?  Create a new LV, make the new filesystem, tar the data over=

 to

> > > it.  When everything is working, delete the old LV.  If you need extra
> > > space during the transition, borrow a drive and add it to the VG.
> > =20
> > What's the benefit of LVM when I add a separate drive?

>=20

> you can add the drive to the VG and then create more LV's to shuffle
> filesystems around to make the conversion possible.


If I had a spare drive I would:

1. copy all data from the "problem" partition
2. do the conversion (a reformat is no problem as everything is backed=20
up
3. copy all data back

Can you do it faster or easier with LVM? I'm just asking, never used=20
LVM.

Regards,
Andrei
--=20
If you can't explain it simply, you don't understand it well enough.
(Albert Einstein)

--RDS4xtyBfx+7DiaI
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFGtAw9qJyztHCFm9kRAg3wAJ9bGNrc9UzOmsLecnx7BExcVrElGQCggKi+
gk4tFKJLAwT8IyjBc9rK5Gk=
=zA4N
-----END PGP SIGNATURE-----

--RDS4xtyBfx+7DiaI--



Date: Sat, 04 Aug 2007 00:16:31 -0500
From: "Mumia W.." <paduille.4061.mumia.w+nospam@earthlink.net>
To: Debian User List <debian-user@lists.debian.org>
Subject: Re: Opinions XFS
Message-ID: <46B40BAF.70800@earthlink.net>
Content-Type: text/plain; charset=US-ASCII; format=flowed
Content-Transfer-Encoding: 7bit

On 08/03/2007 09:44 PM, David Brodbeck wrote:

> [...]
> I think there's a bit of Not Invented Here syndrome with XFS that causes 
> people to be wary of it, but in my experience it's a rock-solid 
> filesystem.  However, it doesn't journal data, only metadata, so you may 
> lose a bit of data if the system goes down uncleanly.  The filesystem 
> will be protected from corruption, however.  (Ext3fs can also be 
> configured this way, but its default is to journal data as well as 
> metadata.)
> 


Huh?

It was my understanding that, by default, ext3 only journals metadata. 
You have to use one of the "journal_data*" options specified in "man 
tune2fs" to get ext3 to journal data.


Do you need more help?X

Date: Sat, 04 Aug 2007 00:22:12 -0500
From: "Mumia W.." <paduille.4061.mumia.w+nospam@earthlink.net>
To: Debian User List <debian-user@lists.debian.org>
Subject: Re: Opinions XFS
Message-ID: <46B40D04.1010904@earthlink.net>
Content-Type: text/plain; charset=iso-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable

On 08/03/2007 10:37 PM, Sergio Belkin wrote:

> --- El Vie 03 Ago 2007, michael@estone.ca encontr=F3 un teclado y tipe=F3=

 lo=20

> siguiente:=20

>> mi: XFS and grub do not work nicely together, therefore you'll need /b=
oot =20
>> mi: mounted with EXT3, everything else can be XFS, even / .
>> mi:
>=20

> And What about lilo?

>=20

Most probably, LILO will work with any filesystem that Linux can use=20
because LILO creates a load map that allows the LILO bootloader to=20
operate independently of the filesystem.

I haven't tested it, but I can't see any reason why LILO wouldn't work=20
with XFS or any other filesystem. Just remember to always do=20
"/sbin/lilo" after any changes to /etc/lilo.conf, the kernel, message=20
file, splash image, or any other file that LILO needs to boot.

End of debian-user-digest Digest V2007 Issue #2095
**************************************************

Received on Sat Aug  4 02:03:01 2007

This archive was generated by hypermail 2.1.8 : Thu Aug 09 2007 - 19:05:39 EDT

Contact Us  Legal Notices  Order Services Online 
Pantek Home  Privacy Policy  IT news  Site Map  Pantek Library