public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
* [gentoo-user] gentoo testing and ssd
@ 2012-07-13 17:42 Allan Gottlieb
  2012-07-13 18:16 ` Stefan G. Weichinger
  2012-07-13 20:42 ` Volker Armin Hemmann
  0 siblings, 2 replies; 11+ messages in thread
From: Allan Gottlieb @ 2012-07-13 17:42 UTC (permalink / raw
  To: gentoo-user

I will be getting a new laptop with ssd (250GB).

I currently run ~amd64 and wonder if this is too much writing for the
flash.

I have adapted to and now enjoy gnome3.  If I were forced to run stable
to limit compiles I would still use package.accept_keywords to permit
gnome3.

Any experiences with testing and ssd?

thanks,
allan



^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: [gentoo-user] gentoo testing and ssd
  2012-07-13 17:42 [gentoo-user] gentoo testing and ssd Allan Gottlieb
@ 2012-07-13 18:16 ` Stefan G. Weichinger
  2012-07-13 18:53   ` Allan Gottlieb
  2012-07-13 20:42 ` Volker Armin Hemmann
  1 sibling, 1 reply; 11+ messages in thread
From: Stefan G. Weichinger @ 2012-07-13 18:16 UTC (permalink / raw
  To: gentoo-user

Am 2012-07-13 19:42, schrieb Allan Gottlieb:
> I will be getting a new laptop with ssd (250GB).
> 
> I currently run ~amd64 and wonder if this is too much writing for the
> flash.
> 
> I have adapted to and now enjoy gnome3.  If I were forced to run stable
> to limit compiles I would still use package.accept_keywords to permit
> gnome3.
> 
> Any experiences with testing and ssd?

No problems with ~amd64 and gnome3 on SSD in my ThinkPad, for maybe 2yrs
already.

My main workstation was migrated back to a shiny new SSD yesterday, the
first SSD there was flaky ... (used one, cheap from the net, no warranty
...)

Stefan



^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: [gentoo-user] gentoo testing and ssd
  2012-07-13 18:16 ` Stefan G. Weichinger
@ 2012-07-13 18:53   ` Allan Gottlieb
  2012-07-13 19:17     ` Stefan G. Weichinger
  0 siblings, 1 reply; 11+ messages in thread
From: Allan Gottlieb @ 2012-07-13 18:53 UTC (permalink / raw
  To: gentoo-user

On Fri, Jul 13 2012, Stefan G. Weichinger wrote:

> Am 2012-07-13 19:42, schrieb Allan Gottlieb:
>> I will be getting a new laptop with ssd (250GB).
>> 
>> I currently run ~amd64 and wonder if this is too much writing for the
>> flash.
>> 
>> I have adapted to and now enjoy gnome3.  If I were forced to run stable
>> to limit compiles I would still use package.accept_keywords to permit
>> gnome3.
>> 
>> Any experiences with testing and ssd?
>
> No problems with ~amd64 and gnome3 on SSD in my ThinkPad, for maybe 2yrs
> already.

Thank you.  That is just want I wanted to know.
allan



^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: [gentoo-user] gentoo testing and ssd
  2012-07-13 18:53   ` Allan Gottlieb
@ 2012-07-13 19:17     ` Stefan G. Weichinger
  2012-07-13 19:53       ` Allan Gottlieb
  0 siblings, 1 reply; 11+ messages in thread
From: Stefan G. Weichinger @ 2012-07-13 19:17 UTC (permalink / raw
  To: gentoo-user

Am 2012-07-13 20:53, schrieb Allan Gottlieb:
> On Fri, Jul 13 2012, Stefan G. Weichinger wrote:
> 
>> Am 2012-07-13 19:42, schrieb Allan Gottlieb:
>>> I will be getting a new laptop with ssd (250GB).
>>>
>>> I currently run ~amd64 and wonder if this is too much writing for the
>>> flash.
>>>
>>> I have adapted to and now enjoy gnome3.  If I were forced to run stable
>>> to limit compiles I would still use package.accept_keywords to permit
>>> gnome3.
>>>
>>> Any experiences with testing and ssd?
>>
>> No problems with ~amd64 and gnome3 on SSD in my ThinkPad, for maybe 2yrs
>> already.
> 
> Thank you.  That is just want I wanted to know.

Be sure to check for the latest firmware for the SSD and flash it before
even using it. Also check for any well known issues with the particular
SSD. And a decent backup strategy is never a bad thing ;-)

With that flaky ssd I had scripts to quickly rsync the partitions to
hdd-based storage so I could rather quickly switch back and boot from
there. That ssd worked and looked OK for weeks and then *ZIP* changed
its mind and its size to 0 bytes ... that wasn't too funny.

The ssd in my thinkpad is completely robust and problemfree.

S



^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: [gentoo-user] gentoo testing and ssd
  2012-07-13 19:17     ` Stefan G. Weichinger
@ 2012-07-13 19:53       ` Allan Gottlieb
  0 siblings, 0 replies; 11+ messages in thread
From: Allan Gottlieb @ 2012-07-13 19:53 UTC (permalink / raw
  To: gentoo-user

On Fri, Jul 13 2012, Stefan G. Weichinger wrote:

> Am 2012-07-13 20:53, schrieb Allan Gottlieb:
>> On Fri, Jul 13 2012, Stefan G. Weichinger wrote:
>> 
>>> Am 2012-07-13 19:42, schrieb Allan Gottlieb:
>>>> I will be getting a new laptop with ssd (250GB).
>>>>
>>>> I currently run ~amd64 and wonder if this is too much writing for the
>>>> flash.
>>>>
>>>> I have adapted to and now enjoy gnome3.  If I were forced to run stable
>>>> to limit compiles I would still use package.accept_keywords to permit
>>>> gnome3.
>>>>
>>>> Any experiences with testing and ssd?
>>>
>>> No problems with ~amd64 and gnome3 on SSD in my ThinkPad, for maybe 2yrs
>>> already.
>> 
>> Thank you.  That is just want I wanted to know.
>
> Be sure to check for the latest firmware for the SSD and flash it before
> even using it. Also check for any well known issues with the particular
> SSD. And a decent backup strategy is never a bad thing ;-)
>
> With that flaky ssd I had scripts to quickly rsync the partitions to
> hdd-based storage so I could rather quickly switch back and boot from
> there. That ssd worked and looked OK for weeks and then *ZIP* changed
> its mind and its size to 0 bytes ... that wasn't too funny.
>
> The ssd in my thinkpad is completely robust and problemfree.

This would be a new dell laptop (latitude E series).  I do daily backup
of my user data now and will continue with the new laptop.  I hope my
experiences match yours with the thinkpad.

allan



^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: [gentoo-user] gentoo testing and ssd
  2012-07-13 17:42 [gentoo-user] gentoo testing and ssd Allan Gottlieb
  2012-07-13 18:16 ` Stefan G. Weichinger
@ 2012-07-13 20:42 ` Volker Armin Hemmann
  2012-07-13 23:44   ` [gentoo-user] " walt
                     ` (2 more replies)
  1 sibling, 3 replies; 11+ messages in thread
From: Volker Armin Hemmann @ 2012-07-13 20:42 UTC (permalink / raw
  To: gentoo-user; +Cc: Allan Gottlieb

Am Freitag, 13. Juli 2012, 13:42:47 schrieb Allan Gottlieb:
> I will be getting a new laptop with ssd (250GB).
> 
> I currently run ~amd64 and wonder if this is too much writing for the
> flash.
> 
> I have adapted to and now enjoy gnome3.  If I were forced to run stable
> to limit compiles I would still use package.accept_keywords to permit
> gnome3.
> 
> Any experiences with testing and ssd?
> 
> thanks,
> allan

one ssd for /
one ssd for /home

ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  
WHEN_FAILED RAW_VALUE
  9 Power_On_Hours          0x0032   098   098   000    Old_age   Always       
-       8277
 12 Power_Cycle_Count       0x0032   099   099   000    Old_age   Always       
-       850
175 Program_Fail_Count_Chip 0x0032   100   100   010    Old_age   Always       
-       0
176 Erase_Fail_Count_Chip   0x0032   100   100   010    Old_age   Always       
-       0
177 Wear_Leveling_Count     0x0013   093   093   017    Pre-fail  Always       
-       398
178 Used_Rsvd_Blk_Cnt_Chip  0x0013   083   083   010    Pre-fail  Always       
-       10
179 Used_Rsvd_Blk_Cnt_Tot   0x0013   097   097   010    Pre-fail  Always       
-       48
180 Unused_Rsvd_Blk_Cnt_Tot 0x0013   097   097   010    Pre-fail  Always       
-       1872
181 Program_Fail_Cnt_Total  0x0032   100   100   010    Old_age   Always       
-       0
182 Erase_Fail_Count_Total  0x0032   100   100   010    Old_age   Always       
-       0
183 Runtime_Bad_Block       0x0013   100   100   010    Pre-fail  Always       
-       0
187 Reported_Uncorrect      0x0032   100   100   000    Old_age   Always       
-       0
195 Hardware_ECC_Recovered  0x001a   200   200   000    Old_age   Always       
-       0
198 Offline_Uncorrectable   0x0030   100   100   000    Old_age   Offline      -       
0
199 UDMA_CRC_Error_Count    0x003e   253   253   000    Old_age   Always       
-       1
232 Available_Reservd_Space 0x0013   083   083   010    Pre-fail  Always       
-       50
233 Media_Wearout_Indicator 0x0032   099   099   000    Old_age   Always       
-       2156

and

ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  
WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x000f   094   094   050    Pre-fail  Always       
-       0/6002739
  5 Retired_Block_Count     0x0033   100   100   003    Pre-fail  Always       
-       2
  9 Power_On_Hours_and_Msec 0x0032   098   098   000    Old_age   Always       
-       1924h+46m+24.900s
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       
-       256
171 Program_Fail_Count      0x0032   000   000   000    Old_age   Always       
-       2
172 Erase_Fail_Count        0x0032   000   000   000    Old_age   Always       
-       0
174 Unexpect_Power_Loss_Ct  0x0030   000   000   000    Old_age   Offline      -       
5
177 Wear_Range_Delta        0x0000   000   000   000    Old_age   Offline      -       
0
181 Program_Fail_Count      0x0032   000   000   000    Old_age   Always       
-       2
182 Erase_Fail_Count        0x0032   000   000   000    Old_age   Always       
-       0
187 Reported_Uncorrect      0x0032   100   100   000    Old_age   Always       
-       0
194 Temperature_Celsius     0x0022   030   030   000    Old_age   Always       
-       30 (Min/Max 30/30)
195 ECC_Uncorr_Error_Count  0x001c   120   120   000    Old_age   Offline      -       
0/6002739
196 Reallocated_Event_Count 0x0033   100   100   003    Pre-fail  Always       
-       2
201 Unc_Soft_Read_Err_Rate  0x001c   120   120   000    Old_age   Offline      -       
0/6002739
204 Soft_ECC_Correct_Rate   0x001c   120   120   000    Old_age   Offline      -       
0/6002739
230 Life_Curve_Status       0x0013   100   100   000    Pre-fail  Always       
-       100
231 SSD_Life_Left           0x0013   100   100   010    Pre-fail  Always       
-       0
233 SandForce_Internal      0x0000   000   000   000    Old_age   Offline      -       
910
234 SandForce_Internal      0x0032   000   000   000    Old_age   Always       
-       786
241 Lifetime_Writes_GiB     0x0032   000   000   000    Old_age   Always       
-       786
242 Lifetime_Reads_GiB      0x0032   000   000   000    Old_age   Always       
-       2457

testing, kde, + kde-testing overlay

but:
/var 
and PORTDIR not on ssd.

seriously, intel had once some calculations that even with lots of daily 
writes you could go on for years as long as you did not fill up the ssd 
completely.

-- 
#163933



^ permalink raw reply	[flat|nested] 11+ messages in thread

* [gentoo-user] Re: gentoo testing and ssd
  2012-07-13 20:42 ` Volker Armin Hemmann
@ 2012-07-13 23:44   ` walt
  2012-07-14  0:14     ` Volker Armin Hemmann
  2012-07-14 15:40   ` [gentoo-user] " Allan Gottlieb
  2012-07-14 20:28   ` Mark Knecht
  2 siblings, 1 reply; 11+ messages in thread
From: walt @ 2012-07-13 23:44 UTC (permalink / raw
  To: gentoo-user

On 07/13/2012 01:42 PM, Volker Armin Hemmann wrote:
> Am Freitag, 13. Juli 2012, 13:42:47 schrieb Allan Gottlieb:
>> I will be getting a new laptop with ssd (250GB).
>>
>> I currently run ~amd64 and wonder if this is too much writing for the
>> flash.
>>
>> I have adapted to and now enjoy gnome3.  If I were forced to run stable
>> to limit compiles I would still use package.accept_keywords to permit
>> gnome3.
>>
>> Any experiences with testing and ssd?
>>
>> thanks,
>> allan
> 
> one ssd for /
> one ssd for /home
> 
> ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  
> WHEN_FAILED RAW_VALUE
>   9 Power_On_Hours          0x0032   098   098   000    Old_age   Always       
> -       8277
>  12 Power_Cycle_Count       0x0032   099   099   000    Old_age   Always       
> -       850
> 175 Program_Fail_Count_Chip 0x0032   100   100   010    Old_age   Always       
> -       0
> 176 Erase_Fail_Count_Chip   0x0032   100   100   010    Old_age   Always       
> -       0
> 177 Wear_Leveling_Count     0x0013   093   093   017    Pre-fail  Always       
> -       398
> 178 Used_Rsvd_Blk_Cnt_Chip  0x0013   083   083   010    Pre-fail  Always       
> -       10
> 179 Used_Rsvd_Blk_Cnt_Tot   0x0013   097   097   010    Pre-fail  Always       
> -       48
> 180 Unused_Rsvd_Blk_Cnt_Tot 0x0013   097   097   010    Pre-fail  Always       
> -       1872
> 181 Program_Fail_Cnt_Total  0x0032   100   100   010    Old_age   Always       
> -       0
> 182 Erase_Fail_Count_Total  0x0032   100   100   010    Old_age   Always       
> -       0
> 183 Runtime_Bad_Block       0x0013   100   100   010    Pre-fail  Always       
> -       0
> 187 Reported_Uncorrect      0x0032   100   100   000    Old_age   Always       
> -       0
> 195 Hardware_ECC_Recovered  0x001a   200   200   000    Old_age   Always       
> -       0
> 198 Offline_Uncorrectable   0x0030   100   100   000    Old_age   Offline      -       
> 0
> 199 UDMA_CRC_Error_Count    0x003e   253   253   000    Old_age   Always       
> -       1
> 232 Available_Reservd_Space 0x0013   083   083   010    Pre-fail  Always       
> -       50
> 233 Media_Wearout_Indicator 0x0032   099   099   000    Old_age   Always       
> -       2156
> 
> and
> 
> ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  
> WHEN_FAILED RAW_VALUE
>   1 Raw_Read_Error_Rate     0x000f   094   094   050    Pre-fail  Always       
> -       0/6002739
>   5 Retired_Block_Count     0x0033   100   100   003    Pre-fail  Always       
> -       2
>   9 Power_On_Hours_and_Msec 0x0032   098   098   000    Old_age   Always       
> -       1924h+46m+24.900s
>  12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       
> -       256
> 171 Program_Fail_Count      0x0032   000   000   000    Old_age   Always       
> -       2
> 172 Erase_Fail_Count        0x0032   000   000   000    Old_age   Always       
> -       0
> 174 Unexpect_Power_Loss_Ct  0x0030   000   000   000    Old_age   Offline      -       
> 5
> 177 Wear_Range_Delta        0x0000   000   000   000    Old_age   Offline      -       
> 0
> 181 Program_Fail_Count      0x0032   000   000   000    Old_age   Always       
> -       2
> 182 Erase_Fail_Count        0x0032   000   000   000    Old_age   Always       
> -       0
> 187 Reported_Uncorrect      0x0032   100   100   000    Old_age   Always       
> -       0
> 194 Temperature_Celsius     0x0022   030   030   000    Old_age   Always       
> -       30 (Min/Max 30/30)
> 195 ECC_Uncorr_Error_Count  0x001c   120   120   000    Old_age   Offline      -       
> 0/6002739
> 196 Reallocated_Event_Count 0x0033   100   100   003    Pre-fail  Always       
> -       2
> 201 Unc_Soft_Read_Err_Rate  0x001c   120   120   000    Old_age   Offline      -       
> 0/6002739
> 204 Soft_ECC_Correct_Rate   0x001c   120   120   000    Old_age   Offline      -       
> 0/6002739
> 230 Life_Curve_Status       0x0013   100   100   000    Pre-fail  Always       
> -       100
> 231 SSD_Life_Left           0x0013   100   100   010    Pre-fail  Always       
> -       0
> 233 SandForce_Internal      0x0000   000   000   000    Old_age   Offline      -       
> 910
> 234 SandForce_Internal      0x0032   000   000   000    Old_age   Always       
> -       786
> 241 Lifetime_Writes_GiB     0x0032   000   000   000    Old_age   Always       
> -       786
> 242 Lifetime_Reads_GiB      0x0032   000   000   000    Old_age   Always       
> -       2457
> 
> testing, kde, + kde-testing overlay
> 
> but:
> /var 
> and PORTDIR not on ssd.
> 
> seriously, intel had once some calculations that even with lots of daily 
> writes you could go on for years as long as you did not fill up the ssd 
> completely.

Are you using a non-journaling filesystem?
 






^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: [gentoo-user] Re: gentoo testing and ssd
  2012-07-13 23:44   ` [gentoo-user] " walt
@ 2012-07-14  0:14     ` Volker Armin Hemmann
  0 siblings, 0 replies; 11+ messages in thread
From: Volker Armin Hemmann @ 2012-07-14  0:14 UTC (permalink / raw
  To: gentoo-user; +Cc: walt

Am Freitag, 13. Juli 2012, 16:44:57 schrieb walt:
> On 07/13/2012 01:42 PM, Volker Armin Hemmann wrote:
> > Am Freitag, 13. Juli 2012, 13:42:47 schrieb Allan Gottlieb:
> >> I will be getting a new laptop with ssd (250GB).
> >> 
> >> I currently run ~amd64 and wonder if this is too much writing for the
> >> flash.
> >> 
> >> I have adapted to and now enjoy gnome3.  If I were forced to run stable
> >> to limit compiles I would still use package.accept_keywords to permit
> >> gnome3.
> >> 
> >> Any experiences with testing and ssd?
> >> 
> >> thanks,
> >> allan
> > 
> > one ssd for /
> > one ssd for /home
> > 
> > ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED
> > WHEN_FAILED RAW_VALUE
> > 
> >   9 Power_On_Hours          0x0032   098   098   000    Old_age   Always
> > 
> > -       8277
> > 
> >  12 Power_Cycle_Count       0x0032   099   099   000    Old_age   Always
> > 
> > -       850
> > 175 Program_Fail_Count_Chip 0x0032   100   100   010    Old_age   Always
> > -       0
> > 176 Erase_Fail_Count_Chip   0x0032   100   100   010    Old_age   Always
> > -       0
> > 177 Wear_Leveling_Count     0x0013   093   093   017    Pre-fail  Always
> > -       398
> > 178 Used_Rsvd_Blk_Cnt_Chip  0x0013   083   083   010    Pre-fail  Always
> > -       10
> > 179 Used_Rsvd_Blk_Cnt_Tot   0x0013   097   097   010    Pre-fail  Always
> > -       48
> > 180 Unused_Rsvd_Blk_Cnt_Tot 0x0013   097   097   010    Pre-fail  Always
> > -       1872
> > 181 Program_Fail_Cnt_Total  0x0032   100   100   010    Old_age   Always
> > -       0
> > 182 Erase_Fail_Count_Total  0x0032   100   100   010    Old_age   Always
> > -       0
> > 183 Runtime_Bad_Block       0x0013   100   100   010    Pre-fail  Always
> > -       0
> > 187 Reported_Uncorrect      0x0032   100   100   000    Old_age   Always
> > -       0
> > 195 Hardware_ECC_Recovered  0x001a   200   200   000    Old_age   Always
> > -       0
> > 198 Offline_Uncorrectable   0x0030   100   100   000    Old_age   Offline 
> >     - 0
> > 199 UDMA_CRC_Error_Count    0x003e   253   253   000    Old_age   Always
> > -       1
> > 232 Available_Reservd_Space 0x0013   083   083   010    Pre-fail  Always
> > -       50
> > 233 Media_Wearout_Indicator 0x0032   099   099   000    Old_age   Always
> > -       2156
> > 
> > and
> > 
> > ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED
> > WHEN_FAILED RAW_VALUE
> > 
> >   1 Raw_Read_Error_Rate     0x000f   094   094   050    Pre-fail  Always
> > 
> > -       0/6002739
> > 
> >   5 Retired_Block_Count     0x0033   100   100   003    Pre-fail  Always
> > 
> > -       2
> > 
> >   9 Power_On_Hours_and_Msec 0x0032   098   098   000    Old_age   Always
> > 
> > -       1924h+46m+24.900s
> > 
> >  12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always
> > 
> > -       256
> > 171 Program_Fail_Count      0x0032   000   000   000    Old_age   Always
> > -       2
> > 172 Erase_Fail_Count        0x0032   000   000   000    Old_age   Always
> > -       0
> > 174 Unexpect_Power_Loss_Ct  0x0030   000   000   000    Old_age   Offline 
> >     - 5
> > 177 Wear_Range_Delta        0x0000   000   000   000    Old_age   Offline 
> >     - 0
> > 181 Program_Fail_Count      0x0032   000   000   000    Old_age   Always
> > -       2
> > 182 Erase_Fail_Count        0x0032   000   000   000    Old_age   Always
> > -       0
> > 187 Reported_Uncorrect      0x0032   100   100   000    Old_age   Always
> > -       0
> > 194 Temperature_Celsius     0x0022   030   030   000    Old_age   Always
> > -       30 (Min/Max 30/30)
> > 195 ECC_Uncorr_Error_Count  0x001c   120   120   000    Old_age   Offline 
> >     - 0/6002739
> > 196 Reallocated_Event_Count 0x0033   100   100   003    Pre-fail  Always
> > -       2
> > 201 Unc_Soft_Read_Err_Rate  0x001c   120   120   000    Old_age   Offline 
> >     - 0/6002739
> > 204 Soft_ECC_Correct_Rate   0x001c   120   120   000    Old_age   Offline 
> >     - 0/6002739
> > 230 Life_Curve_Status       0x0013   100   100   000    Pre-fail  Always
> > -       100
> > 231 SSD_Life_Left           0x0013   100   100   010    Pre-fail  Always
> > -       0
> > 233 SandForce_Internal      0x0000   000   000   000    Old_age   Offline 
> >     - 910
> > 234 SandForce_Internal      0x0032   000   000   000    Old_age   Always
> > -       786
> > 241 Lifetime_Writes_GiB     0x0032   000   000   000    Old_age   Always
> > -       786
> > 242 Lifetime_Reads_GiB      0x0032   000   000   000    Old_age   Always
> > -       2457
> > 
> > testing, kde, + kde-testing overlay
> > 
> > but:
> > /var
> > and PORTDIR not on ssd.
> > 
> > seriously, intel had once some calculations that even with lots of daily
> > writes you could go on for years as long as you did not fill up the ssd
> > completely.
> 
> Are you using a non-journaling filesystem?

ext4

-- 
#163933



^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: [gentoo-user] gentoo testing and ssd
  2012-07-13 20:42 ` Volker Armin Hemmann
  2012-07-13 23:44   ` [gentoo-user] " walt
@ 2012-07-14 15:40   ` Allan Gottlieb
  2012-07-14 20:28   ` Mark Knecht
  2 siblings, 0 replies; 11+ messages in thread
From: Allan Gottlieb @ 2012-07-14 15:40 UTC (permalink / raw
  To: Volker Armin Hemmann; +Cc: gentoo-user

On Fri, Jul 13 2012, Volker Armin Hemmann wrote:

> Am Freitag, 13. Juli 2012, 13:42:47 schrieb Allan Gottlieb:
>> I will be getting a new laptop with ssd (250GB).
>> 
>> I currently run ~amd64 and wonder if this is too much writing for the
>> flash.
>> 
>> I have adapted to and now enjoy gnome3.  If I were forced to run stable
>> to limit compiles I would still use package.accept_keywords to permit
>> gnome3.
>> 
>> Any experiences with testing and ssd?
>> 
>> thanks,
>> allan
>
> one ssd for /
> one ssd for /home
>

[[ snip ]]

> testing, kde, + kde-testing overlay
>
> but:
> /var 
> and PORTDIR not on ssd.
>
> seriously, intel had once some calculations that even with lots of daily 
> writes you could go on for years as long as you did not fill up the ssd 
> completely.

I will be sure to keep some empty space.
thanks,
allan



^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: [gentoo-user] gentoo testing and ssd
  2012-07-13 20:42 ` Volker Armin Hemmann
  2012-07-13 23:44   ` [gentoo-user] " walt
  2012-07-14 15:40   ` [gentoo-user] " Allan Gottlieb
@ 2012-07-14 20:28   ` Mark Knecht
  2012-07-14 22:53     ` Volker Armin Hemmann
  2 siblings, 1 reply; 11+ messages in thread
From: Mark Knecht @ 2012-07-14 20:28 UTC (permalink / raw
  To: gentoo-user; +Cc: Allan Gottlieb

On Fri, Jul 13, 2012 at 1:42 PM, Volker Armin Hemmann
<volkerarmin@googlemail.com> wrote:
<SNIP>
> testing, kde, + kde-testing overlay
>
> but:
> /var
> and PORTDIR not on ssd.
>

So you have these on a HDD? /var for large write count reasons and
PORTDIR for size reasons?

Thanks,
Mark



^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: [gentoo-user] gentoo testing and ssd
  2012-07-14 20:28   ` Mark Knecht
@ 2012-07-14 22:53     ` Volker Armin Hemmann
  0 siblings, 0 replies; 11+ messages in thread
From: Volker Armin Hemmann @ 2012-07-14 22:53 UTC (permalink / raw
  To: gentoo-user; +Cc: Mark Knecht, Allan Gottlieb

Am Samstag, 14. Juli 2012, 13:28:32 schrieb Mark Knecht:
> On Fri, Jul 13, 2012 at 1:42 PM, Volker Armin Hemmann
> <volkerarmin@googlemail.com> wrote:
> <SNIP>
> 
> > testing, kde, + kde-testing overlay
> > 
> > but:
> > /var
> > and PORTDIR not on ssd.
> 
> So you have these on a HDD? /var for large write count reasons and
> PORTDIR for size reasons?

mostly because 64 gb is not so much ;) 
But sparing the ssd a lot of writes is an additional bonus.

and not on one hdd but 3... a raid5. 

-- 
#163933



^ permalink raw reply	[flat|nested] 11+ messages in thread

end of thread, other threads:[~2012-07-14 22:55 UTC | newest]

Thread overview: 11+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2012-07-13 17:42 [gentoo-user] gentoo testing and ssd Allan Gottlieb
2012-07-13 18:16 ` Stefan G. Weichinger
2012-07-13 18:53   ` Allan Gottlieb
2012-07-13 19:17     ` Stefan G. Weichinger
2012-07-13 19:53       ` Allan Gottlieb
2012-07-13 20:42 ` Volker Armin Hemmann
2012-07-13 23:44   ` [gentoo-user] " walt
2012-07-14  0:14     ` Volker Armin Hemmann
2012-07-14 15:40   ` [gentoo-user] " Allan Gottlieb
2012-07-14 20:28   ` Mark Knecht
2012-07-14 22:53     ` Volker Armin Hemmann

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox